Automation fails when I add Epic Name as a condition

[Tamra Avery]

Hi -

I'm trying to create an automation that creates sub-tasks when I add a task. The automation works perfectly until I add a condition that limits the automation to a specific epic (Epic Name contains a specific value). As soon as I add the Epic Name condition, the automation fails. Any suggestions?

[John Funk]

Hi Tamra,

Why type of project is it? Next-gen? Classic Software?

If Classic Software, try using the Epic Link field

If Next-gen, try using the parent field. 

[Gerardo Romero]

Hi John,

I'm using Jira Cloud and I'm having the same issue in a Classic Software project. Epic Link filed is not available in automation "Issue fields condition" step and adding the Epic Name reports "The following issues did not match the condition:" once trying the automation.

[John Funk]

Hi @Gerardo Romero  - are you still having this problem? 

@Tamra Avery  - any update? 

[Gerardo Romero]

Hi @John Funk - Yes, I'm having the same issue, Epic Link is not available.

But I want to mention I used a workaround adding an Advanced compare condition and using the {{issue.epic.key}} value to make the condition. Not the most elegant way but it works.

[John Funk]

Great - glad you at least have a work around, which sounds like it is the probable solution.  

[Azamat Dalabayev]

Hey, @Gerardo Romero !

Can you please share the solution that you use to solve the problem usin {{issue.epic.key}} value?

Can't get how to overcome the issue with the JQL as I don't have options to query my the epic name via epic.key...

Thanks in advance

[John Funk]

@Tamra Avery  - If you are good now, can you click on the Accept Answer button above so we can close this one out? Thanks!

[Gerardo Romero]

Hey @Azamat Dalabayev ,

What I did is add an Advanced compare condition.

• Click on Add Component
• Click on New Condition
• Select Advanced compare condition
• In first value use {{issue.epic.key}} and in the second field the EPIC ID

Best

[Azamat Dalabayev]

I see. I wasn't very clear in my question.

Thanks for answer, @Gerardo Romero

Actually, what I though you overcame and what I need - is how using Epic.Key to query Epic name. Might be out of scope of the topic, and moreover might be out of scope for jira automation as well. But if you have an idea - you are more than welcome to share it :)))