Automation - parent inherits status by its least progressed subtask

[david_kubac]

I would like to set up an automation that checks the statuses of parent's subtasks and updates the parent task status accordingly. However, I don't need just a copy/paste of the status of one specific subtask but rather the status of the least progressed subtask.

Now I know that the Workflow varies by each organization and that it's not really linear, so within the automation, I need to specify based on which condition it should inherit the status.

Let's establish 4 different statuses:

1. Backlog
2. Todo
3. In progress
4. Done

The trigger most likely would be a subtask status change.

What happens next is the part I don't know how to do.

What I need to happen when any subtask changes its status is to validate all other subtasks to see, if I should trigger the parent change. Not only that, but I need to make it linear.

You can imagine something like:

1. Are there any subtasks with status Backlog?
   1. if yes, set the parent status to Backlog and stop the automation
   2. if no, continue with the next condition
2. Are there any subtasks with status Todo?
   1. if yes, set the parent status to Todo and stop the automation
   2. if no, continue with the next condition
3. Are there any subtasks with status In Progress?
   1. if yes, set the parent status to In Progress and stop the automation
   2. if no, continue with the next condition
4. Are there any subtasks with the status Done?
   1. if yes, set the parent status to Done and stop the automation
   2. if no, continue with the next condition

Any idea, how to achieve this?

[Thomas Schlegel · Accepted solution]

Hi @chris.west,

completed issues are the issues that reached the mostright column of your board. 

If you put the "Done"and the "Close" - status there, the Completed-Count should be fine.

[chris.west]

Thank you Thomas, based on that I realised the 'cards' are only reflecting the data shown in the board, so I had to assign all the issue types to a column.

:)

[chris.west]

Apologies, I meant workflow statuses to a column, not issue types!