Do not change state without the Child closed

[Nicolas Mayans]

Hello community, I hope you are doing well! I have a question regarding the closing of incidents. They asked me if it is possible that when you try to close a task, Father will prohibit it if it has unclosed daughter tasks. Greetings!

[Trudy Claspill · Accepted solution]

Hello @Nicolas Mayans 

What is the issue type hierarchy that you are working with? The native issue type hierarchy in Jira is:

Epic
|-- standard level issue types (i.e. Story, Task, Bug)
    |-- subtask level issue types

Are you trying to prevent closure of an Epic, or closure of issue types at the "standard level"?

Also what is the Project Type of the project where you want to set this restriction? You can get that information from the Type column on the View All Projects page.

[Nicolas Mayans]

Hi Trudy, I hope you're doing well. We have these types of hierarchies. Initiative, Epic, Task, Sub Task. And they want an Initiative to not be closed if the Epics are not closed.

[Trudy Claspill]

Hello Nicolas,

There is not a native Condition or Validator in workflows for what you want to do. There are a couple of options available to you.

1. You could add a custom field to Initiatives that keeps track of how many open Epics there are under the Initiative. You would have to use Automation Rules to update that field as the status of Epics was changed. Then you could add a Condition or Validator to the transition to Done for the Workflow used by Initiatives to allow the transition only when the field value is 0. 

2. You could look into third party apps that add more functionality to Jira Workflows and through them find a method to add a Condition or Validator that would look at the status of the child Epics of the Initiative.

[Nicolas Mayans]

Thank you very much Trudy, the answer is very helpful.
Greetings!