...
| Info |
|---|
This is the documentation |
...
for JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, |
...
Maintain consistency across projects and get a clear view of your team's tasks
Do you want to make your parent issue close when all the issues in it are closed?
JSU Automation suite for Jira workflows can help you automate it.
Check how to set up the JSU post-function 'Linked transition'.
Check out the "How to" video further below to configure your automation.
How to configure this workflow
Go to your project settings and click to edit your workflow. Choose the transition you want to add your post function in. In this case we will choose the ‘Done’ transition number 31. Change to the post functions tab and add a post function. Choose the ‘Linked transition’ post function from the menu and add it.
Now configure your post function. You want your epic to turn to done when all tasks are done, so choose your transition to be triggered on Epic. Choose the transition you want the epic to perform when the issues are done. Here we want the epic to turn to Done too. Make sure you choose the Done transition with the corresponding number – here it’s 31. You don’t need to add a resolution to the done transition. In case you want one, you have to make sure that the resolution field is visible on the transition screen.
Since we only want to close the Epic when the last task is closed, we need to configure the status of the sibling issues. In this case we choose the status “Done” so that the linked transition will be executed only if all tasks in the Epic are done. Click add to move on with your JSU automation and publish your workflow.
Now go to your Epic and turn all the tasks to “done”. Your epic status is now “done” too! You can configure the same automation process for any parent and sub-tasks you need.
...
Watch this video to see all of this in action*:
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
This was only a bit of JSU in action. Subscribe to our YouTube channel and Access more JSU use cases.
See also the app documentation for some more examples and configuration screenshots.
*The video is created on the Jira Server environment.
...
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 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.
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. Click the arrow that points to this status to show the transition rule options menu.Status colour Green title DONE 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.
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 theDonetransition. 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 its subtasks are alsoStatus 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 set this asStatus colour Green title DONE 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!