Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 43 Current »

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.


Eliminate repetitive tasks and save time by automatically closing parent tasks


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.


Linked Transition post function

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 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.

  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 let's set the Trigger transition on all issues related as option to Parent / Subtask > Parent (Issue in Transition must be Sub-Task).

  7. Next, we define which transition and in which workflow we want to transition the parent issue we just selected. We want to keep this rule simple, so we only want this rule to apply to issues in our JSU project.
    Transition: We select the workflow that applies to our JSU project and the Done transition. This means 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. 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 set this as Done.

  9. The remaining fields are optional. For your reference we consider how you might want to use these fields. If you're happy as is, feel free to proceed to Step 9. 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, 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 go 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!

    Congratulations! You've just configured your very own automation! (star)

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!

  • No labels