Hello,
I'm trying to have a rule condition based on Epic Link name.
I managed to make it work based on Epic Link key but that's not my final goal.
I could get the Epic link name through branching, but I cannot find a way back to update my issue with this info (I'm in the Epic branch and can only update my Epic values).
What I've tried based on the structure I can see in the parent :
{{issue.Epic Link}} ==> provides me NNT-8
{{issue.Epic Link.summary}} ==> KO
{{issue.Epic Link.fields.summary}} ==> KO
{{issue.Epic Link.fields.summary}} ==> KO
{{issue.parent.key}} ==> KO
{{issue.fields.parent.key}} ==> KO
{{issue.parent.summary}} ==> KO
{{issue.parent.fields.summary}} ==> KO
I'm guessing issue.parent is not accessible, and issue.Epic Link only contains the Epic key.
My questions :
How can I get my issue Epic Link name ?
Is it possible to access issue.parent ?
Is it possible to get an epic name by key (like {{issue.MyKey.summary) ?
Thanks.
Hi @BAILLEUL LOIC and welcome to Community!
{{issue.Epic link.Summary}} works on my end:
Could you please check your rule audit log to see which error you are getting?
- Manon
Thanks for your help, made me realise I was inversing my Summary value and my Epic Name value.
{{issue.Epic Link.Epic Name}} did the trick :)
BTW from your screenshot I discovered the "testing" feature through manual rule trigger & logging (no longer having to create a new issue for each test is a blessing), is there any documentation available for best testing practices ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad it helped!
There isn't any official documentation about testing but I wrote an article to share automation best practices: 🪄 New automation rule checklist
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @BAILLEUL LOIC ,
As I can see in your original post you are already working on a solution and providing good information on your solution.
In order to provide the right solution I always try to understand the context and the purpose from a functional perspective.
May I ask you to therefore describe your need as a use case? (often seen use case descriptions in "given - when - then" format):
Thanks in advance.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.