Hello,
I have configured a story template in Jira that contains 10 sequentially ordered subtasks, each assigned to a different individual. The workflow requires each subtask to be blocked until the completion of its preceding subtask. The purpose of this template is to facilitate the creation of multiple instances of this story for repetitive tasks, all within a larger epic.
Currently, the subtasks do not automatically update their status based on the completion of the previous tasks, which leads to inefficiencies and delays since assignees are not promptly informed when it is their turn to begin work. To manage this, I manually set all subtasks to "Blocked" and only change the status when the preceding task is completed.
I have attempted to establish dependencies using "is blocked by" and "blocks" relationships, but it seems these are only visible as tags on the tickets without actively controlling the flow or notifications.
Questions:
Any guidance on setting up a more automated and efficient workflow for these repetitive and dependent tasks would be greatly appreciated.
Thank you!
Hello @Musa Aqeel
Welcome to the Atlassian community.
There isn't a pre-built solution native to Jira.
You could use Automation Rules to achieve your goal.
You can use Issue Transitioned as the trigger, triggering the rule based on the blocking issue changing to a particular status.
You can use For Each Related Issue: Linked Issues to change the focus to the linked/dependent issue.
You can the send a notification or change the status or otherwise take an action on the dependent issue.
https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.