Implementing Sequential Task Dependencies in a Reusable Story Template

Musa Aqeel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 30, 2024


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.


  1. Is there an existing feature or plugin that can automate the blocking/unblocking of subtasks based on the completion status of the previous subtasks within a template?
  2. Can notifications be configured to alert the next assignee when their subtask is unblocked and ready to begin?
  3. Am I approaching the automation of this sequential task dependency in the right way, or is there a more effective method to achieve the desired workflow?

Any guidance on setting up a more automated and efficient workflow for these repetitive and dependent tasks would be greatly appreciated.

Thank you!

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 30, 2024

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events