Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation for subtasks


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"


2 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
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.
Mar 26, 2023

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,

Thank you very much!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events