How to automatically transition the Parent issue based on the Sub-task status
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
The information on this page relates to customizations in JIRA Applications. Consequently, Atlassian Support cannot guarantee the provision of any support for the steps described on this page as customizations are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.
Summary
Use Case sample: If any of one sub-task status change from "Open" to "In Progress" then automatically the Parent issue status should be changed to "In Progress".
Solution
This is a common request from multiple Jira users.
We are sharing some ideas on how to achieve this using automation. Feel free to give some more ideas and feedback about other ways to achieve the same goal.
Solution 1: Using Automation for Jira Add-on
- Create a rule on the desired Project to be triggered when a sub-task is transitioned.
- Although the issue that triggered the automation is the sub-task, the conditions and actions should be executed for the parent of the sub-task. We need to open a separate branch for the parent.
- On the Parent's branch, add the condition to check if the parent is still as "To-do" and then add an action to transition the parent to "In Progress".
Note: This use case is using the same workflow status for Parent and subtask, thus "In Progress" does exist on both Parent and Subtask.
- Running the rule:
Goal: When one of the subtasks is moved to "In Progress" from "Open", transition also the parent to "In Progress". On the samples below, Bug's subtask and Epic's subtask were moved to "In Progress".
- Audit Log shows the execution of the rule for both transitions:
Solution 2: Using JSU Automation Suite for Jira Workflows Add-on
- On the workflow used by the sub-task, we added a new post-function triggered at the transition to "In Progress":
- We did select the "Linked Transition (JSU) post-function:
- At the "Trigger transition on all issues related as", select "Parente/Sub-Task and the option "Parent (Issue in Transition must be Sub-Task)" and the target of the transition, "In Progress":
