Automation for subtasks

[Nitzan Matalon]

Hey guys,

Im trying to create an automtaion for related subtasks (with same parent).

A short explanation:

If subtask's component=! QA, it is a dev subtasks.

If subtask's component= QA, it is qa subtask

I want to create an automtaion: if a qa subtask status= to do, and all of its related DEV subtasks are closed, then only the QA subtask is transtioned to "ready for qa" status.

I tried this automation but I keep getting at the audit log: "no actions performed"

[Bill Sheboy · Accepted solution]

Hi @Nitzan Matalon 

I suspect the problem with this rule is the branch for this scenario AND testing for sub-tasks of sub-tasks. 

You do not indicate how many of each type of sub-task (i.e. QA and not QA) exist for a parent, so I would recommend a different approach...

Using either the Related Issues condition with JQL, or Lookup Issues followed by an Advanced Compare condition, test each thing once.

• trigger: issue transitioned
• condition: issue is a sub-task
• condition: the component is not-QA
• use one of the above techniques to confirm the QA sub-task(s) are all in "to do"
• use one of the above techniques to confirm the not-QA sub-task(s) are all completed
• now you can branch to the QA sub-task(s) to transition them to Ready for QA

Kind regards,
Bill

[Nitzan Matalon]

Thank you very much!