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

Stop Epic from closing if unresolved stories/tasks


I would like to Stop Epic from closing if unresolved stories/tasks, These are not like Sub task blocking condition.

2 answers

Hi @Murugan Mittapalli and team, 

Please find below a solution applicable to Cloud Jira (Premium or Enterprise, as long as you got access to Automations) which doesn't rely on third party add-ons (e.g. JSU, JMWE or Scriptrunner).

1. Create a custom number field (e.g. EpicClosure or FeatureClosure)

2. Add a "Value Field" Condition to the Done/Cancelled Epic Workflow transition to allow closing only if the EpicClosure is 1).

3. Create an automation rule to set EpicClosure to 1 when all the Stories which link up to the Epic are Done/Cancelled.

(When: Issue Transitioned - For Epic (parent) - if: Stories match Status in (Done, Cancelled) - then: Edit issue fields EpicClosure to 1).

4: Create a second automation rule to set EpicClosure to 0 when Stories aren't all in Done or Cancelled.

(When: Issue Transitioned - For Epic (parent) - if: Stories match Status not in (Done, Cancelled) - then: Edit issue fields EpicClosure to 0).

Hope this helps and have a good one.

Luca Calderone 

Jira Admin

Neat idea.

I believe it needs a 3rd automation rule for new Stories created

(When: Issue Created - For Epic (parent) - if: Stories match Status not in (Done, Cancelled) - then: Edit issue fields EpicClosure to 0).

Like # people like this

Hi @Lucian Marginean ,

Thanks for pointing this out, you're completely right!

Like Eli Albert likes this

@Luca Calderone  @Lucian Marginean 

This is a really great idea!  but what about the following scenario:

some epics don't have any child issues, so in this case the field" EpicClosure" will always be empty and the transition will be blocked...

Do you have any solution for this?

and indeed, for epics that have child issue this is an excellent solution.


Like Eli Albert likes this
2 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 06, 2018

Hello Murugan,

Thanks for reaching out to us with this inquiry.  It is possible to achieve the required functionality by utilizing a Condition provided by the Jira Misc Workflow Extensions plugin.  Once you install this plugin, you can follow the below steps to force the Epic to remain open until all child Stories are close:

  1. Edit the workflow
  2. Modify the transition that leads to your Epic's closed status (e.g., Done, Resolved, Closed)
  3. Click on the Conditions tab -> Add condition link
  4. Select 'Linked Issues Status Condition (JMWE add-on)' -> Add button
  5. Choose 'is Epic of (from Epic to Stories)' -> check the relevant closed statuses
  6. Click Add button
  7. Publish your workflow

~Andrew Sweeten
Atlassian Support

Thank you for your reply Andrew, Can we use Script runner to resolve this.

@ASweeten - I found this via a google search. We have JMWE installed on our cloud instance, but I don't see any conditions added by JMWE. I do see (and have used) JMWE-specific post-functions. We used the add-on in our on-prem install, and conditions are available.

I just checked the knowledgebase for the add-on, and it indicates that due to the Connect framework for Cloud, conditions and validators are no longer available via the add-on, but have been integrated natively into Jira Cloud.

So where can I find the Linked Issue condition you mentioned in your answer? I'm not seeing it...


David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 13, 2018

Unfortunately, only the Conditions and Validators that were available in JMWE for Jira Server mid-2016 were integrated natively into Jira Cloud, and the Linked Issues Status Condition isn't one of them.

Unfortunately, until Atlassian makes configurable Conditions and Validators available to apps, you won't find any solution to your problem on Jira Cloud.

Thanks for the response, @David Fischer _Appfire_. Not the answer I was hoping for, but I can't say I'm surprised.

Suggest an answer

Log in or Sign up to answer