Info |
---|
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
| ||||||
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
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
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
status. ClickStatus colour Green title DONE
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.
In the Post Functions table - click "
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 let's set
the Trigger transition on all issues related as
option to
Parent /
Subtask > Parent (Issue in Transition must be Sub-Task)
.
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
as part of the rule we're configuring.Status colour Green title DONE
We only want the parent to be transitioned to
if ALL of itsStatus colour Green title DONE
subtasks are also
. To configure this, forStatus colour Green title DONE
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
.
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.
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.
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.
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.
Now you're ready to save your new post function. To do this,
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 go test the post function in action!
Go to an open issue that
includes one or more open
subtasks.
Transition all of the subtasks to
.Status colour Green title done
Refresh/reload the parent issue. You'll notice that it has now also been transitioned to
- which means our post function has worked as expected!Status colour Green title done
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!