Automation: Don't allow an epic to transition to done if children are not done

[Scott Hassell]

Issue:   Epics are being moved to done while children are still open.  Would like an automation to prevent epics from moving to done state until all children have been completed.

[Nacho Moreno Ortega]

Hi @Scott Hassell ,

I am Nacho and i am part of Decadis.

If using a third party app is an option for you, i would recommend to use a validator from our app Jira Workflow Toolbox.

We have this specific case on the following page of our documentation, which you can easily implement in your instance: Block a transition if some issues under an epic are not in a certain status.

If you require assistance with this implementation, please do not hesitate to contact us via our support portal.

Best regards,

Nacho 

[Shalini Pradhan]

Hello @Scott Hassell ,

Good day! Welcome to Atlassian Community :)

Automation cant prevent a transition but it can automatically revert the epic back if someone moves it to Done when all child workitems are not done.

Trigger: Workitem transitioned

• Status changed to: Done

• For workitem types: Epic

Condition: Related issues condition

• Related issues: Child issues 

• Condition:Some match specified JQL -> Add JQL:  Statuscategory = Done

Action: Transition issue

• Transition the epic back to its previous status, example select In progress

[Trudy P Claspill]

Hello @Scott Hassell 

An Automation flow is triggered when an event completes; i.e. the transition to done has already completed. They can't be used to block the transition directly.

Some alternatives:

1. An Automation flow triggered when the Epic transitions to done, which checks if there are any not done children. The flow can either automatically re-open the epic or send an email to a responsible party directing them to review and address the non-compliance.

2. A custom field in the Epic that will keep track of how many child items are not done. This custom field would need to be set by an Automation flow. The Automation flow could be scheduled to review Epics periodically to see if they have open children and update the custom field accordingly. Or an Automation flow could be triggered based on status changes to items that are children of Epics, review all the child items of the Epic, and update the custom field in the Epic. This alternative is more complex because you would also need to consider when child items are added to the Epic or removed from the Epic.

3. Use of a third party app to create a custom Rule to implement in the workflow used by the Epic. 

Let us know if you have additional questions.

[Marc -Devoteam-]

Hi @Scott Hassell 

The suggestion from @Shalini Pradhan is a fine option.

But as others mention, automations trigger on actions, they don't prevent an action to happen.

Best is to do this via the workflow, but ootb there is no condition or validator for this, you would need a 3rd party marketplace app.

You could look at:

• JMWE
• JWT
• JSU
• Scriptrunner

[Mikael Sandberg]

Automations are running after an action is done, it cannot prevent something to happen like a transition. You could do this as part of your workflow to prevent the transition to be shown until all linked work items are done.

[Mikael Sandberg]

It can be done by either have a field on the epic that sets the number of open child work items, or you would need an app that restrict it based in parent - child link.