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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

how to automatically close an epic based on linked issue status

I am looking at using automations for this but cannot seem to get the right recipe together for this to execute. 


How would i go about automatically transitioning an epic to done once all linked issues are marked done?

4 answers

2 accepted

0 votes
Answer accepted

Hey all, thank you for your help. I found the issue in the end was not the automation but rather there was a duplicate "EPIC LINK" custom field that was not the system default. That is what was breaking the automation.

Jack Brickey Community Leader Dec 09, 2020

DOH! I have seen it many times where people create a custom field with the same name as a system field. 

Like # people like this

Oh my...  Hopefully this issue can be resolved/mitigated in the future, such as with project references to fields:


0 votes
Answer accepted
Jack Brickey Community Leader Dec 09, 2020

Hi Scott, do you really mean "linked" issues or do you mean issues that are associated to an Epic via the Epic Link. Just want to be clear as there is a difference.

Here is what I have used to close the epic once all stories are done.


Gahhhh. That is exactly what i had.  Seems really simple and straight forward but it didnt work


Jack Brickey Community Leader Dec 09, 2020

i have had mine disabled for some time now (don't need it really) but it certainly was working as I recall. What does your log say?

Hey @Jack Brickey heres what i see. This is currently only applied to the QAA project and that is where im testing this too.


Jack Brickey Community Leader Dec 09, 2020

i will need to test on my end when i get a second.

Jack Brickey Community Leader Dec 09, 2020

Just re-enabled, tested and worked....


John Funk Community Leader Dec 09, 2020

The only difference I see is that one has ="Done" and the other has =done

Hi @Scott Federman 

Is this a Classic or a NextGen project?

If you go to the condition with the JQL status check, and click on the link "validate query" what does it show?

Best regards,


@John Funk made that change and still nothing


@Bill Sheboy Its a classic project and when i validate it returns 451 issues.

In my case problem was in empty assignee field. After I assigned someone to all issue in epic it started to work. 

0 votes
John Funk Community Leader Dec 09, 2020

Hi Scott,

Have you already started one that is not working? If so, can you share that one? And what is not working with it. 

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events