Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation changes one sub-task but not the other

Lydia M
Contributor
November 6, 2020

I have an automation rule: When parent is Ready for QC→ move all sub-tasks to Ready for QC. I have two subtasks, RAD and QC; both have a status "Ready for QC." The automation works for the RAD sub-task, but not the QC sub-task. I can't figure out why. Any thoughts?

1 answer

0 votes
Chris Buzon
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 6, 2020

Check the rule "scope", it may be set for only 1 or a specific number of projects.  That's found in rule details.

If this is set so both (or all) projects can access the rule, check the audit log for that rule - you will find the other sub-task that moved somewhere, and near that entry you should see the one that indicates why it failed.  Be warned, fail messaging can be pretty non-specific. It's just a breadcrumb to follow.



chrome_2020-11-06_15-14-53.png

Lydia M
Contributor
November 6, 2020

Hi, Thanks for the suggestion, but both of the sub-tasks are of the same parent issue in one project. But the scope advice will come in handy in the future, I'm sure!

Chris Buzon
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 6, 2020

Have you found the rules audit log?  Whatever the problem is, there should be a message saying that issue123 did not meet specific criteria.  That will help reverse engineer the problem.

From your description, I am not sure what RAD-subtask vs QC-subtask means.  If the issue Keys (QA-123 vs BV-123) are different letters at the start, then they are actually different projects and may have different rules to follow.
The fact that they have the same parent doesn't necessarily matter, and the fact they have the same status names also isn't the whole picture.  If there is a required field for the QC subtask to transition but not for the RAD subtask, it would fail to transition the QC subtask.

Can you take a screenshot of an example of the issue? It's important to see exactly what you mean by RAD-subtask and QC-subtask.

Lydia M
Contributor
November 6, 2020

Hi Chris,

 

Sorry to confuse you. RAD and QC are the names of my sub-tasks. They have nothing to do with issue keys.

We can say sub-task 1 and sub-task 2, or sub-tasks a & b if it's easier to understand.

Like Chris Buzon likes this
Lydia M
Contributor
November 6, 2020

I'm actually going to start over from scratch, but thank you for trying to help me.

Cheers!

Like Chris Buzon likes this
Chris Buzon
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 6, 2020

OK, that helps.  If you can take a screenshot of your rules steps it will help.  Without that, it's all just a guess on my part.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events