nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

All comments

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_ozedzo

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_ozedzo

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud