move story (Parent) to ready for testing only when all dev sub tasks moved to done

Ahmad Abdelhafiz July 14, 2023

the automation trigger without any action. move the story (Parent) to ready for testing only when all dev sub-tasks are moved to done, Igone other sub-tasks type.

 

2023-07-14_09-29-07.png

 

2023-07-14_09-33-17.png

 

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 14, 2023

Hello @Ahmad Abdelhafiz 

Welcome to the Atlassian community!

Can you provide more information on where you need help? Is the rule not operating the way you expect it to? What is it doing, or not doing, compared to your expectations?

Ahmad Abdelhafiz July 14, 2023

thanks for your quick response, we have 4 different sub tasks type, and I need the parent to transition the status only when the last dev sub task moved to done. 

Ahmad Abdelhafiz July 14, 2023

For example, I have a story (Parent) that has the following sub-tasks:

1- 4 Dev sub-tasks

2- 3 UI sub-tasks

3- 2 QA sub-tasks

the rule will trigger the automation and move the story (the parent) ready for testing only when the 4th Dev sub-task is moved to done regardless of the other sub-tasks type status.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 14, 2023

Thanks for that additional information.

It is not possible to refine the Trigger itself to have the rule triggered for a transition for only for a specific issue type, but you can add a Condition after the trigger to check the issue type of the triggering issue. If the triggering issue is not the specified type, then the rule will be exited.

Screen Shot 2023-07-14 at 10.05.38 AM.png

 

Within the branch for the Parent use two Related Issues condition. With the first confirm that some of the subtasks are the targeted type and are set to Done. With the second confirm that there are no subtasks of the targeted type that are not set to Done. In my example I am using "QA Subtask".

Screen Shot 2023-07-14 at 10.10.07 AM.png

Those conditions will ignore the existence and status of any other types of subtasks.

Then, finally, make the desired change to the Parent issue.

Ahmad Abdelhafiz July 14, 2023

Thank you so much @Trudy Claspill , you are the best. highly appreciated. it worked

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events