Transition User Story to "READY FOR TEST" status when all Developer sub-task get Done

[Tâm_ Nguyễn Thanh]

We have a User Story with developer sub-tasks and QC sub-task

I want to auto-transition User Story to "READY FOR TEST" status when all developer sub-tasks have been Done.

Please help to create automation rules for this,

Many thanks!

[Trudy Claspill · Accepted solution]

Hello @Tâm_ Nguyễn Thanh 

How do you distinguish developer sub-tasks from QC sub-tasks? Are they different sub-task issue types?

Have you attempted to construct this automation rule? If so, please show us what you have so far.

[Tâm_ Nguyễn Thanh]

Yes, inside a User story, we create Developer sub-tasks distinguish from QC sub-task, Developer sub-tasks and QC sub-task are different issue type

We want to move the User story status from CODING to READY FOR TEST when all Developer sub-tasks have DONE

We attempted to construct the rule by using JQL to compare the number of Developer sub-tasks (1) with the number of Developer sub-task has DONE (2), if (1) = (2) then User story will transition from CODING to READY FOR TEST, but this not work because JQL collected all sub-task not only the subtask inside the certain User story

[Trudy Claspill]

Please show us the automation rule you constructed.

Please show us the Audit Log details for the execution of that rule.

Please show us the issue for which the rule is being run that goes with the audit log details.

Please show us the issue types that are available to the project so that we can confirm if the Development sub-task and the QC sub-task are separate issue types.

[Tâm_ Nguyễn Thanh]

bellow is the content of the rule

(the sub-task represent developer sub-task as mentioned above)

[Tâm_ Nguyễn Thanh]

This is list of issue types:

[Tâm_ Nguyễn Thanh]

this is the user story for testing the rule

[Tâm_ Nguyễn Thanh]

There is no error recorded in the audit log

[Trudy Claspill]

This is the rule that you need.

In the JQL where I have 

or issuetype="QC Sub-task"

...you need to include all the possible sub-task types that you want to ignore that could exist under the parent issue.

or (issuetype in ("QC_SubTask", "BA_SubTask", "Sub-Bug"))

The net effect of the condition is to check all the Sub-tasks under the specified parent and confirm that

- all the development sub-tasks ("Sub-task") are in a status=Done

- any other sub-tasks types can exist under the parent and their statuses don't matter

If there is a development sub-task that is not done, the condition will fail.

The problem with your condition is that you are simply doing a JQL match and your JQL doesn't include a condition to check that the sub-tasks being evaluated belong to the parent issue you are working against.

Even though you selected the Related Issues condition, you still have to have something in the condition that defines the relationship between the parent and the issues you are checking.

When you select "Sub-tasks" as the Related Issue value, then the condition know that you want to look at the sub-tasks only of the parent issue you are working against. When you choose JQL, you have to add criteria to your JQL to constrain the sub-tasks it finds to be the sub-tasks of just the parent issue you are working against.

[Tâm_ Nguyễn Thanh]

Thank you, Trudy, It's worked!