bgColor | #f5f5f5 |
---|---|
titleColor | #ffffff |
borderWidth | 0 |
titleBGColor | #000000 |
title | JSU for Jira Server/Data Center |
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 parent issues are automatically closed when all of its sub-tasks are completed
↓ Follow the visual step-by-step guide below to see how to configure this automation in your Jira instance. ↓
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
into "Diagram Mode"
As weto Diagram mode.
We want to close parent issues when
its' sub-taskstheir subtasks are done, so we need to add the rule specifically to when issues transition to the
status. Click onStatus colour Green title DONE the arrow that points
inwardsto this status to show the transition rule options menu.
As weWe want to add a
Post-Functionpost function to this transition
, whichthat runs an automation after the issue has been transitioned to the target status. Select
"Post Functions
"from the
list which opens a newoptions list to display the Post Functions tab.
In the Post Functions table - click "Select Add post function
"to view all available post
-functions.
- Choose "
Select the Linked Transition (JSU)
"post function, and then click
"Add
"at the bottom of the
screenpage.
- As we
We want the parent to
beautomatically
closedclose when the last
sub-task is Closed -subtask is closed, so let's set
"the Trigger transition on all issues related as
" to "option to
Sub-Task > ParentParent /
"Subtask > Parent (Issue in Transition must be Sub-Task)
.
- Now
Next, we
have to tell JSUdefine which transition and in which workflow
do wewe want to transition the
Parentparent issue we just selected.
As weWe 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
as part of the rule we're configuring.Status colour Green title DONE
But remember, we We only want the parent to be transitioned to
if ALL of it's sub-tasksStatus colour Green title DONE its subtasks are also
. To configure this, for "Status 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
're going toset this as
"
"Done
.
The remaining fields are optional. For your reference
thoughwe
can talk aboutconsider how you might want to use
the remainingthese 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.
Resolution - If you would like to add a
Resolutionresolution to the parent issue after the post
-function closes it, you can define which
Resolutionresolution 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
ranrun 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-Functionpost function. To do this,
click "select Add
"at the bottom of the page.
You can now see a
preview summarysummary of all your
Post-Functionspost 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 likepage, select Publish Draft. You can choose to save a backup
of the workflow before our changes are applied, followed by "Publish" again.if required before confirming.
Test the post function in the workflow
Now we can go test the post
-function in action!
HeadGo to an open issue that
hasincludes one or more open
sub-tasks within itsubtasks.
Now proceed to transitionTransition all of the subtasks to
.Status colour Green title done - Now refresh
Refresh/reload the parent issue. You'll notice that it has now also been transitioned to
- which means our Post-FunctionStatus colour Green title done post function has worked as expected!
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!
Need more
information or help? Get in touch!