Restricting Transition to Done of Epics until all child issues are in Closed, Cancelled, Done

[david.phillips]

We have attempted to implement this requirement using the native workflow transition rules in Jira Cloud using the "Restrict based on the status of subtasks" rule; however, the case of a child issue not in Closed, Cancelled or Done (as desired) restricting the move is not prevented.  Suggestions?  Is this a known deficit on Epics?

[Marc -Devoteam- · Accepted solution]

Hi @david_phillips 

Parent/child relation between an Epic and a Story is not a sub-taks relation, so the sub-tasks condition in the workflow doesn't work for this.

This is not possible without 3rd party apps to extended workflow options.

Als see this feature request, JRACLOUD-79291 

[John Funk]

Totally missed that in the question. You are spot on. 

[John Funk · Accepted solution]

Hi David,

A couple of things - are all of those Statuses in the Done category of statuses (Green). Second, are you setting the Resolution field when work items move into those statuses (post function on the transition to the status in the workflow)?

[david.phillips]

Thanks @John Funk The Features are getting Resolution set to Done or Cancelled

[Valerie Knapp · Accepted solution]

Hi @david_phillips , thanks for your post.

Please can you share some screens of your configuration to show what you have done so far and what you think isn't working?

There is an automation rule in the template library to help with this - https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112177 . You could have a look and see if this helps.

Best wishes

[david.phillips]

Thanks, Valerie! I am not a fan of automating the closure step because I want active validation by EOs, PM/POs. Still, I'll discuss with my LACE colleagues and test today

[Valerie Knapp]

Hi @david_phillips , thanks for sharing the screen. As @Marc -Devoteam-  correctly points out, if this is a condition for an Epic workflow, this won't work as the Epic's children are the standard work item type objects, not the sub-tasks. You cannot enforce this validation if you 'skip' a level in the hierarchy. Does that make sense?

You could block the transition of an Epic if the Stories / Task children are still open, but not subtasks.

[david.phillips]

Thanks @Valerie Knapp I got the bit about the native rule only examining sub-tasks.  In this case, the child issues are Features, one level down in the hierarchy.  Does this require another type of validator?

[John Funk]

One level below Features is not sub-tasks. The validator specifically mentions sub-tasks, not Child tasks or children as Valerie pointed out above. So, yes, it would take a third party tool like JMWE or ScriptRunner to prevent that in the workflow.