Is there a way to require tasks to be completed in sequential order?

[Michael Frade]

Want to see if there is a way ( with sub-tasks or regular task, any issue types) to create tickets and assign them out and make them required to be completed in sequential order.  So there is parent ticket and then task 1 must be completed before task 2 can start/be completed, before task 3 can start/be completed and so on...? I know you can require a sub task to be completed before parent can be closed but wondering about the specific task order being organized in the manner explained above.

[Florian Bauer]

Hi @Michael Frade ,

An easy way to control how issues are created (serially, in parallel or based on decision gateways) is with Flower - BPM Automations for Jira:

As shown above, you can use a graphical process editor to define how your tasks are created in a transparent way. No scripts, conditions or automations are required for this. Here is the link to the Marketplace listing: https://marketplace.atlassian.com/1220753

Happy automating,
Florian

[Trudy Claspill]

Hello @Michael Frade 

For clarity, when you say you want to require them to be completed in order do you mean you actually want to block the transition of issues to a specified "in progress" status if their predecessor is not yet in a "done" status?

Also, what problem are you trying to solve with this requirement? Are you trying to impose a business process to the order of work? Is there a functional limitation in the completion of the tasks that you want to enforce through process in Jira (i.e. the task "walk through doorway" functionally can't be started/completed before completion of task "open door").

[Laurie Sciutti]

Hi @Michael Frade ~ is it necessary to have all sub-tasks created at the same time?  If not, you can create an Automation Rule that generates each subsequent sub-task on transition to Done of the dependency sub-task...

So:

• closing sub-task 1 will autogenerate sub-task 2
• closing sub-task 2 will autogenerate sub-task 3
• etc.

[Michael Frade]

I had thought of that, but was more looking to have all tasks created to start and then requiring them to be worked on in an specific order, even if it was the ticket # order.