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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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?

3 answers

2 accepted

0 votes
Answer accepted
Jack 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 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 heres what i see. This is currently only applied to the QAA project and that is where im testing this too.


Jack Community Leader Dec 09, 2020

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

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

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 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
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
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

640 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you