Automation - Parent transition when all specific labelled sub-tasks are Done

[Oscar Calvo]

Hey Community!

I need to create a new automation: 

The scenario is the following:

I have a Story with some sub-tasks. These sub-tasks have different labels: "Analysis", "Development" and "Testing". So, what I neet to do is:

When a sub-task with label "Analysis" is moved to Done

If all sub-tasks with label "Analysis" are Done

And NO sub-task with label "Development" are In Progress,

Then move the parent to "Ready for Development"

Else move the parent to "In Progress"

How can I do that? THANKS!!

[Walter Buggenhout · Accepted solution]

Hi @Oscar Calvo and welcome to the Community!

For inspiration, have a look at this sample rule from the template library (direct link to the rule ):

That should give you a fairly decent framework to get going. Update the conditions in this sample rule to match your situation.

Since adding an if ... else ... block can't be added under a branch (the for parent part in the rule) you may need to set up 2 separate rules for your 2 scenarios.

Hope this helps!

[Oscar Calvo]

Thank you for your response, @Walter Buggenhout ! :D

Yes, in fact I found this template that you suggest me and I am using it, but I am having a lot of problems with the condition If all sub-tasks with label = "Analysis" are with status = "Done". I am not able to solve it! :(

I have it like this way:

[Oscar Calvo]

Can you see where can I fix this problem? :)

Thanks!

[Walter Buggenhout]

I think I can see the problem, but not a solution in your current approach. I suppose you use the "if all sub-tasks match ..." option to check your conditions. But since you have sub-tasks labelled analysis and other sub-tasks labelled development, you will never be able to make that work (there will always be sub-tasks that make the if all sub-tasks match "labels = analysis" fail.

I obviously don't know what your process looks like, but maybe you should take a step back and look at the way you've set up your process as a whole. If you build analysis and development as statuses/stages into the workflow of your parent issues, you may be able to get rid of the additional check you currently try to embed in your sub-tasks using labels.

In short: if your parent issues have a workflow like this: Backlog > In analysis > Ready for Dev > In development > Ready for Review > In Review > Done (just a high level example), you could just check if all sub-tasks are done when your parent is in analysis and move your parent to Ready for Dev. It would let you eliminate the additional check on sub-task labels that is now blocking your conditions.

[Walter Buggenhout]

Hi @Oscar Calvo,

You may try something like this to isolate the analysis sub-tasks done codition:

 

[Oscar Calvo]

Yes @Walter Buggenhout !! It worked!!! Thank you soooo much!! :D