Close Parent Issue When All Subtasks Are Closed - Legacy

This is the documentation for JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, see our JSU Server/Data Center documentation.

Goal	Eliminate repetitive tasks and save time by automatically closing parent tasks
Scenario	When your team has closed all of an issue’s subtasks, the parent issue remains open and someone has to manually move it to DONE. Let’s look at how this common task can be automated with JSU.
Components	Linked Transition post function

How to configure this rule

Create a draft of your project workflow. If you're unsure how to get to this page, follow the onboarding steps in Edit a Jira Workflow. You can then view your workflow in Text or Diagram mode. The steps in this use case represent Diagram mode. If you haven't already, switch the workflow viewer to Diagram mode.
We want to close parent issues when their subtasks are done, so we need to add the rule specifically to when issues transition to the DONE status. Click the arrow that points to this status to show the transition rule options menu.
We want to add a post function to this transition that runs an automation after the issue has been transitioned to the target status. Select Post Functions from the options list to display the Post Functions tab.
Select Add post function to view all available post functions.
Select the Linked Transition (JSU) post function, and then click Add at the bottom of the page.
We want the parent to automatically close when the last subtask is closed, so we select Parent/Sub-task > The parent of the subtask(s).
Next, we define the workflow and transition that we want to apply to the parent issue we selected. We want to keep this rule simple, so we only want this rule to apply to issues in our JSU project.
We select the workflow that applies to our JSU project and the Done transition. Any parent issues will be transitioned to DONE as part of the rule we're configuring.
We only want the parent to be transitioned to DONE if ALL of its subtasks are also DONE. We set the conditional status to DONE.
The remaining fields are optional. All of these fields are described in detail in the Linked Transition post function page of the Configuration Guide.
Now you're ready to save your new post function. Select Add at the bottom of the page.
You can now see a summary of all your post functions applied to this transition. To confirm this new workflow and test it out, you need to publish it. At the top of the page, select Publish Draft. You can choose to save a backup if required before confirming.

Test the post function in the workflow

Now we can test the post function in action!

Go to an open issue that includes one or more open subtasks.
Transition all of the subtasks to DONE.
Refresh/reload the parent issue. You'll notice that it has now also been transitioned to DONE - which means our post function has worked as expected!

Congratulations! You've just configured your very own automation!

Feel free to continue exploring other use cases for this post function, such as Close parent Epic when all the issues within the Epic are done, and more!

Need more information or help? Get in touch!