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!
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.
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
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.
bellow is the content of the rule
(the sub-task represent developer sub-task as mentioned above)
It looks like you're new here. Sign in or register to get started.
