Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,120
Community Members
 
Community Events
185
Community Groups

When trying to create automation and check for Epic name it doesnt work

Trying to create an automation rule. This is a Next-gen project. 

I need to add subtasks automatically to a story when they created in a specific EPIC. 

I coded to check the (issue type = story) AND (epic name = <specific name>), but the audit log shows that the conditions didn't match. When I changed and looked for (issue type = story) AND (summary contains <keyword>) everything worked fine. 

Tried doing different things for the EPIC but it just doesn't match. I tried contains, and a bunch of other tests, searching for the id of the EPIC

Any suggestions out there? Is this a bug?

 

 

2 answers

Hi @Edmond Melkomian 
While a bit late, you might go about this differently. Rather than trying to match the text of a specific Epic Name or Epic Summary, if you just want to match a specific epic, you could trigger off the JQL, which would be: parentEPIC = ticketnumber

@Cassius Rhue I opened a question with the Atlassian folks, but right now the workaround is to put a keyword, which is not ideal, because some other story in another EPIC if they add that keyword then this workaround doesn't work. 

But I don't know why this doesn't work. Let's see what anyone out there has come up with a solution or this issue. 

Is there an update on this maybe?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events