Page Comparison

How to configure this rule

1. Create a draft of your project workflow. If you're not sure how to get to this page, follow the onboarding steps

1. in Edit a Jira Workflow.

 Keep your backlog clean by ensuring that parent issues are automatically closed when all of their sub-tasks are completed

↓ Follow the step-by-step guide below to see how to configure this automation in your Jira instance. ↓

Configure the post function

1. 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 into "Diagram View" and ensure you are in "Edit Mode". You can enter Edit Mode by selecting the "Edit" option towards the right of your workflow viewer. 
   

   Image Removed

   to Diagram mode.
   

   Image Added

2. We want to close parent issues when their ' sub-tasks subtasks are done, so we need to add the rule specifically to when issues transition to the 

   Status
   colour Green title DONE

    status. Click on the arrow that points inwards to this status to show the transition rule options menu.

3. We want to add a post function to this transition , which that runs an automation after the issue has been transitioned to the target status. Select "Post Functions" from the list which opens a new options list to display the Post Functions tab.
   

   Image Removed

   In the Post Functions table - click "Image Added

4. Select Add post function" to view all available post functions.

   Image Removed

5. Choose "Select the Linked Transition (JSU)" post function, and then click "Add" at the bottom of the screenpage.
   

   Image Removed

6. We want the parent to automatically close when the last sub-task subtask is closed, so let's set "the Trigger transition on all issues related as" to " option to Parent / Sub-Task > Parent Subtask > Parent (Issue in Transition must be Sub-Task)".
   

   Image RemovedImage Added

7. NowNext, we have to tell JSU define which transition and in which workflow we want to transition the parent issue we just selected. As we We want to keep this rule simple, so we only want this rule to apply to issues in our "JSU" project. So for "Transition", we
   Transition: We select the workflow that applies to our JSU project and the "Done" transition. This means any parent issues will be transitioned to 

   Status
   colour Green title DONE

    as part of the rule we're configuring.
   
   Image Removed

   But remember, we Image Added

8. We only want the parent to be transitioned to 

   Status
   colour Green title DONE

    if ALL of its sub-tasks subtasks are also 

   Status
   colour Green title DONE

   . To configure this, for "All other sibling issues (for example linking to the target with the same link type) must have one of the following statuses" we 're going to set this as "Done".
   
   Image RemovedImage Added

9. The remaining fields are optional. For your reference though we can talk about consider how you might want to use the remaining these fields. If you're happy as is, feel free to proceed to Step #99. All of these fields are described in detail in the Linked Transition post function page of the Configuration Guide.

   1. Resolution - If you would like to add a resolution to the parent issue after the post function closes it, you can define which resolution to choose in this field.

   2. Perform as user - In Jira Cloud, all "actions" both manual and automated, must be performed by a registered Atlassian account. If you'd like JSU to impersonate another user to run its automation, you can choose that user here. It's important to note that the impersonated user must have the right account privileges to perform the action. If you're not sure, just leave this field blank. Leaving the field blank means the automation will be run as the default user, "JSU add-on user" which has elevated privileges and can perform most functions.

   3. Copy field - If you'd like to add more information to the parent issue as part of the automation, you can describe what information you'd like to add here.

10. Now you're ready to save your new post function. To do this, click "Add" at the bottom of the page.

    Image Removed

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 screen click "Publish Draft" and then either "Yes" or "No" if you'd like page, select Publish Draft. You can choose to save a backup of the workflow before our changes are applied, followed by "Publish" again. 
    

    Image Removed

    if required before confirming.
    

    Image Added

Test the post function in the workflow

Now we can go test the post function in action!

1. Head Go to an open issue that has includes one or more open sub-tasks within itsubtasks.
   

   Image RemovedNow proceed to transition Image Added

2. Transition all of the subtasks to 

   Status
   colour Green title done

   .
   
   Image RemovedImage Added

3. Now refresh/reload the parent issue. You'll notice that it has now also been transitioned to 

   Status
   colour Green title done

    - which means our post function has worked as expected!
   
   Image RemovedImage Added

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

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