Automation rule to transition parent to a certain status after issues with a certain field are done

[Andrew Distan]

Hi everyone!

(sorry for the long text, i'm trying to be as descriptive as possible)

I'm trying to automate as many processes as i can for my team so they don't need to bother with changing statuses besides for the sub-tasks they are working on and i've hit a bit of a stump:

How can i create a rule that transitions the parent to a certain status when only certain issues with certain fields are set to Done.

Let's say i have a Story with 3 sub-tasks differentiated by field Team: backend, frontend and QA. When backend and frontend are Done, Story should transition to Ready for QA. When QA is Done, Story should transition to Done.

For that i created Rule 1: where all sub-tasks with field Team in (Backend, Frontend) are done, transition story to status Ready for QA.

After that i created Rule 2: where all sub-tasks with field Team in (Backend, Frontend, QA) are Done, Story should transition to Done.

Here i have the following problems:

1. Some Stories only have frontend (or Backend) and QA, so i need the Story to transition to status Ready for QA only when frontend (or Backend) is Done, which does not work with Rule 1 because the rule works only if both Backend and Frontend sub-tasks are available and set to Done.

2. If i change Rule 1 to use "where some sub-tasks" instead of "where all sub-tasks", it will transition Story status to Ready for QA when even one of the Backend or Frontend sub-tasks are done (which is again, not what i'm aiming for, both need to be Done before moving to QA)

3. If i create separate rules for each situation (one for Backend = Done > Move to Ready for QA, one for Frontend = Done > Move to Ready for QA, one for (Backend, Frontend) = Done > Move to Ready for QA) they will interfere with each other, meaning that when either Backend or Frontend is done, it will move to Ready for QA even though the other task is still open.

Any ideas on how to make this work ? It might be that it's not possible to do this with automation, but if anybody has any pointers, i'd appreciate it very much.

 Thank you.

[Bill Sheboy]

Hi @Andrew Distan   -- Welcome to the Atlassian Community!

Thanks for all of the details.  You seem to understand this scenario well, so my recommendation is:

• Diagram out the cases (scenarios with different sub-tasks inputs) and the decision points
• Pick the most restrictive one first; that is your probably first path/rule
• Use Create Variable (or if/else conditions) to track what you have done thus far
• Examine the other cases to see what you need next

This automation library was recently added, and has synchronization scenarios similar to yours; it is a great source for ideas.

https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453

After you have tried that please post any remaining issues so the community can try to help.  Thanks!

Best regards,

Bill