Close Parent Issue When All Subtasks Are Closed

Owned by IT Ops Notifications
Last updated: Jan 16, 2023 by Deborah Scott
2 min read



JSU for Jira Server/Data Center

This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud 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 workflow

  1. Create a draft of your project workflow.

  2. Select the transition you want to add your post function to. In this case, we select the transition to done.

  3. Select the Post Functions tab then click Add post function.

  4. Select the ‘Linked transition’ (JSU) post function then click Add. The post function configuration page displays.

  5. Configure your post function:

    1. We want to move an issue to Done when all its subtasks are done, so for the Trigger transition on all issues related as: option, we select, Parent/Subtask > Parent (issue in transition must be subtask).

    2. Choose the transition that you want to apply to the issue when all the subtasks are done. Here, we want the parent issue to move to Done. You don’t need to add a resolution. If you do include a resolution, make sure that the resolution field is visible on the transition screen.

    3. Since we only want to close the parent issue when the last task is closed, we need to configure the status of all sibling issues. In this case, we choose the Done status so that the linked transition will be executed only once the last subtask is done.

      Screenshot of the configuration options for the Linked Transition post function.

  6. Select Add at the bottom of the page.

  7. Publish your workflow.

  8. Now go to your issue and move all the subtasks to done. Watch as the parent issue moves to done. You may need to refresh your browser to see the change. You can similarly configure the same automation process for an epic and all its subtasks.

This was only a bit of JSU in action. See the app documentation for some more examples and configuration screenshots.