This sample scenario shows you how simple it is to add a JSU automation rule to your workflow.
Have you ever forgotten to close your sub-tasks before you close an issue?
Let’s see how we use JSU to automate the laborious task of closing multiple sub-tasks under a parent issue.
Use case: Automatically close all sub-tasks once the parent issue is closed by using a JSU post-function.
Step 1: Create a draft workflow and select a transition
Under the Transitions column, select “Done (21)”.
.gif?version=1&modificationDate=1568715683315&cacheVersion=1&api=v2&width=511 "JSU for Jira Server/Data Center - edit workflow transition")
Step 2: Add post function
Select the Post Functions tab then click Add post function.
Step 3: Select Linked Transition
Select the Linked transition (JSU) post function then click Add at the bottom of the page.
Step 4: Configure post function
Configure the parameters:
- On the Trigger transition on all issues related as parameter, choose Parent/Sub-task.
- Select All sub-tasks (issue in Transition must be parent).
- In the Transition drop-down menu, select Done (21) to ensure all sub-tasks would move to Done.
- Select your desired resolution status from the Resolution drop-down menu.
- Click Add at the bottom of the page.
- Remember, it is important to click on the “Publish” button inside the yellow box before you move on.
Step 5: Publish the workflow
Step 6: Test your workflow
Once you’ve published your workflow, set up an issue and create as many sub-tasks as you want, in your new (test) project. Move the parent issue to Done and see JSU in action as it automatically moves all sub-task statuses to Done!
| Multimedia | ||||
|---|---|---|---|---|
|
See more examples of JSU in action in our use cases.