Page Comparison

Panel

bgColor	#f5f5f5
titleColor	#ffffff
borderWidth	0
titleBGColor	#000000
title	JSU for Jira Server/Data Center

Info
This is the documentation

of

for JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center,

you can find the documentation here. InfoNOTE: This guide starts from the "Edit Workflow" screen of a chosen project

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

Status

colour	Green
title	done

. Let’s look at how this common task can be automated with JSU.

Components

Linked Transition post function

How to configure this rule

Create a draft of your project workflow. If you're

not sure

unsure how to get to this page, follow the onboarding steps

first on either: /wiki/spaces/JSUCLOUD/pages/27801900 or /wiki/spaces/JSUCLOUD/pages/1147633753

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"
Image Removed
As we
to Diagram mode.
Image Added
We want to close parent issues when
its' sub-tasks
their 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.
As we
We want to add a
Post-Function
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
Select Add post function
"
to view all available post
-
functions.
Image Removed
Choose "
Select the Linked Transition (JSU)
"
post function, and then click
"
Add
"
at the bottom of the
screen
page.
Image Removed
As we
We want the parent to
be
automatically
closed
close 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 Parent /
Sub-Task > Parent
Subtask > Parent (Issue in Transition must be Sub-Task)
"
.
Image RemovedImage Added
Now
Next, we
have to tell JSU
define which transition and in which workflow
do we
we want to transition the
Parent
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
We only want the parent to be transitioned to
Status
colour Green
title DONE
if ALL of
it's sub-tasks
its 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
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
#9
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
  resolution to the parent issue after the post
  -
  function closes it, you can define which
  Resolution
  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
  ran
  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.
Now you're ready to save your new
Post-Function
post function. To do this,
click "
select Add
"
at the bottom of the page.
Image Removed
You can now see a
preview summary
summary of all your
Post-Functions
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!

Head

Go to an open issue that
has
includes one or more open
sub-tasks within it
subtasks.
Image Removed
Now proceed to transition Image Added
Transition all of the subtasks to
Status
colour Green
title done
.
Image RemovedImage Added
Now refresh
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
post function has worked as expected!
Image RemovedImage Added

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