Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Automation : check Epic Name

BAILLEUL LOIC February 16, 2022

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).

 

JiraAutomationEpicLinkName.jpg

 

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

JiraAutomationEpicLinkStructure.jpg

 

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.

2 answers

1 accepted

2 votes
Answer accepted
Manon Soubies-Camy
Community Champion
February 16, 2022

Hi @BAILLEUL LOIC and welcome to Community!

{{issue.Epic link.Summary}} works on my end:

 Capture d’écran 2022-02-16 à 11.58.28.png

Could you please check your rule audit log to see which error you are getting?

- Manon

BAILLEUL LOIC February 16, 2022

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 ?

Like # people like this
Manon Soubies-Camy
Community Champion
February 16, 2022

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 

Like Stefan Salzl likes this
Sherry Goyal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 16, 2022

Hi,

Here is the document to help debug the rule.

Hope this helps!

 

Thanks
Sherry

Like Manon Soubies-Camy likes this
Manon Soubies-Camy
Community Champion
February 16, 2022

Oh I missed that one! Thanks @Sherry Goyal 👍

1 vote
Stefan Salzl
Community Champion
February 16, 2022

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):

  • Preconditions?
  • Entrypoint? --> when exactly would you need "something" to be automated
  • what should then happen? (which information should be given in which direction?)
  • ....

 

Thanks in advance.

Best
Stefan

Suggest an answer

Log in or Sign up to answer