---
title: "Close parent issue when all subtasks are closed - Legacy"
canonical: "https://support.appfire.com/space/JSUCLOUD/12518718/Close%20parent%20issue%20when%20all%20subtasks%20are%20closed%20-%20Legacy"
format: markdown
---
> Macro (aura-html)

---

| **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](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518766) post function |

## How to configure this rule

1. 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](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12519274). 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.
  
2. 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.
3. 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.
  
4. Select **Add post function** to view all available post functions.
5. Select the *Linked Transition (JSU)* post function, and then click **Add** at the bottom of the page.
6. 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)**.** **
7. Next, we define **the workflow** and transition we want to apply to the selected parent issue. 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 for our JSU project and the `Done` transition. Any parent issues will be transitioned to [DONE] as part of the rule we're configuring.
  
8. 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].
9. The remaining fields are **optional**. All of these fields are described in detail in the [Linked Transition](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518766) post function page.
10. Now you're ready to save your new post function. Select **Add** at the bottom of the page.
11. 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.

1. Go to an open issue that includes one or more open subtasks.
  
2. Transition all of the subtasks to [done].
  
3. 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!

---

Need more information or help? [Get in touch!](https://appfire.atlassian.net/servicedesk/customer/portals)