How to "gate" sub-tasks to prevent them being worked on before previous ones are completed?

[Tyler Rathbone]

We have an application change request workflow currently that creates Sub-Tasks as part of an automation, the last 2 sub-tasks are contingent on prior sub-tasks being completed 

Is there a way to prevent them from being worked on until the prior sub-tasks are done?

[Vijay Dadi]

Hello @Tyler Rathbone ,

We achieved this using custom fields and automations and workflow configurations. Have custom field "Sequence Blocked" with values "Yes/No". Whenever a link is created with block/blocks, update the sequence as Yes with an automation. 

Update your workflow with required field condition as "Sequence Blocked" should be No if you want to close the task.

When the task is completed and it has a link as blocks, using an automation you have to set the sequence blocked to "No" so that you can work on it. 

Hope this helps?

Vijay

[Maciej Dudziak _Forgappify_]

Welcome @Tyler Rathbone

I’m afraid that’s not possible in Jira out-of-the-box. However, if you have an app or are open to using one that offers Jira expression-based workflow validators/conditions, it may be achievable. The key question is how you would differentiate sub-tasks that block other sub-tasks. Do they share common attributes, such as a label, issue type, or part of the summary?

[Tyler Rathbone]

Essentially as part of the workflow there's 3 automation rules that create the sub-tasks based on status