How do you automatically transition a Sub-Task of a Story when another Sub-Task is Done?

Martin Walker_qf7evp

We have have an existing Automation Rule that creates a Story within an Epic and auto-creates 21 Sub-Tasks within the Story. The next part we are trying to do is to create a rule that when a certain Sub-Task is moved to Done on the Kanban board it will pull in the next Sub-Task--here is an example.

Columns

Planning > In Progress > Pending > Done

Sub-Tasks

Customer Task 1
Customer Task 2
Customer Task 3
Customer Task 4
Customer Task 5

Here is what we want to happen:

Customer Task 1 is moved to the Done column > Customer Task 2 is moved from Planning to In Progress

Customer Task 2 is moved to the Done column > Customer Task 3 is moved from Planning to In Progress

The process will continue until the last Sub-Task is completed. Please let me know if anyone has any similar rules that they have setup or has any idea of how to get started with this process.

Mark Segall

Hi @Martin Walker and welcome to the community!

You'll need business logic to define "the next sub-task", but the general flow of the rule would be this:

• TRIGGER: Issue Transitioned (To Done)
• BRANCH (JQL)
  • Parent = {{issue}} and <YOUR SUB-TASK LOGIC>
  • ACTION: Transition Issue (To In Progress)