Automation: Move QA sub task to Ready for QA when all Sb-Task are set to Done

[Nikhil Chourasia]

Hi everyone,

I’m trying to set up an automation for our Bug issue type in Jira.

Here’s the use case:

• For every bug, we typically have at least one QA sub-task and one or more development sub-tasks ("Sub-task").

• What I want to achieve is: when all the development sub-tasks are marked as Done, I’d like all the QA sub-tasks under that same bug to automatically transition to “Ready for QA.”

I’ve tried multiple approaches but haven’t been able to get this to work as expected.

Has anyone set up something similar, or could you point me in the right direction? Any help would be appreciated!

Company-Managed Project

Thanks in advance!

[Nikhil Chourasia · Accepted solution]

I solved it using: 

[Bill Sheboy]

Hi @Nikhil Chourasia -- Welcome to the Atlassian Community!

You describe trying multiple approaches and none worked as expected.  What did not work as expected?

For a question like this, context is important for the community to help.  Please post the following:

• what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Kind regards,
Bill

[Nikhil Chourasia]

Hi Bill,

I did mention earlier that it's a company-managed project, but I realize now that I may not have framed my question clearly.

The core issue is that I've tried several approaches—for example, creating a branch on the parent issue—but I haven’t found a way to specifically target only the development sub-tasks, check if they’re all done, and then trigger an action on the QA sub-tasks.

Even when using JQL to branch into sub-tasks or to retrieve sub-tasks under the same parent, I couldn't find a way to first validate that the development sub-tasks are done and then act on the QA sub-tasks.

So, to clarify, I haven’t even been able to reach the point where I could test this properly. Apologies if my original question was unclear.

[Bill Sheboy]

Thanks for the additional information!

Rather than using branching to identify the work items (and their status), I recommend using the Lookup Work Items / Issues action with JQL to find the development subtasks which are not done...followed by a Smart Values Condition to check the count found is 0.

Once you have confirmed your development subtasks are all done, a JQL branch over the QA subtasks may be used to transition the ones not already in the desired status.

[arielei]

Hello @Nikhil Chourasia 

See here, i've answered this:

https://community.atlassian.com/forums/Jira-questions/How-to-transition-a-task-after-multiple-sub-tasks-are/qaq-p/3050875

[Nikhil Chourasia]

In your response, you transitioned the parent task to "Done"—but I already have automation in place for that. What I'm specifically trying to do is transition the QA sub-task to "Ready for QA" once all the development sub-tasks ("Sub-task") are marked as done. So, it's not about moving the parent to "Ready for QA," but about updating the QA sub-task based on the status of the development sub-tasks.