How do I prevent parent issues from being able to close before children??

[Steve Josue]

How do I prevent parent issues from being able to close before children??

Let's use Story and Sub-Task as the example. I beleive in older version JIra enforced that all sub-taks under a Story would have to be closed before the parent story could be closed.

Now, in Jira DataCenter 9.9.0 the Story can be closed regardless of its sub-task's status. Why is this and how can we prevent the possibility of creating all these orphans??

Thanks!

-Steve

[Trudy Claspill · Accepted solution]

Hello @Steve Josue 

I am looking at Jira Data Center v9.4.4.

There it is possible to set a Workflow Transition Condition that requires all Subtasks of an issue to be resolved in order for the transition to be available.

I am not aware of there ever being any other option to globally prevent an issue from being resolved unless all its subtasks were resolved. Nor do I believe there has ever been any such option for other parent/child combinations, like Epics and their child issues.

[Steve Josue]

Hi Trudy, 

I tried to do that in Workflows and in Automation.

Do you have any advice or examples to accomplish a Workflow Transition Condition that requires all Subtasks of an issue to be resolved in order for the transition to be available.

I am falling short, because in workflows on the transition to DONE, just allows for field selection, no Boolean "what if's".

Thanks,

Steve

[Trudy Claspill]

Hello Steve,

When you are editing the workflow and click on the transition to Done you should get an option to view the Triggers, Conditions, Validators, and Post Functions associated with that transition. Do you get that?

Then click on the option to view the Conditions.

Then click on the option to Add a Condition. You should then get a list of the Conditions available to be added.

Can you share a screen image of that list with us?

I believe there should be an option on that list with the name "Sub-Task Blocking Condition ".

[Steve Josue]

My experience was using POST functions only but will go follow these directions and get back to you. Question: We have a separate workflow for Stories/Tasks and one for everything else. Which workflow would this be applied to? The one containing Sub-Tasks? Thanks!

[Trudy Claspill]

Post-functions are for things you want done after the transition has already been completed. You can't use those to prevent a transition.

You would need this Condition to be in the workflow that applies to the issue types where sub-tasks can be added as child issues, i.e. you can create Sub-tasks under a Story so apply the Condition to the Workflow that applies to Stories.

[Steve Josue]

Thats it, it worked perfectly - Thank you Trudy!!!

Steve