You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I've tried to set up an automation that transitions the parent issue from To Do -> In Progress when a child issue is manually transitioned from To Do -> In Progress.
Here's a snip of how I've set it up. What have I got wrong?
Please show us the details from the Audit Log where the execution result is No Actions Performed.
What is the issue type of the "parent" and the "child"?
The "Parent" related issue option works only when the trigger issue is a sub-task type of issue.
That isn't going to work. As I said the Related Issues/ Parent is only appropriate when the trigger issue is a sub-task. The For branch will not find any matching parent issue for any other issue type
If you want the For branch to operate against parent issues that are Epics then you need to select the Related Issues / "Epic (parent)" option instead.
Since you are saying "Trying to diagnose", I might suggest you add Log action entries into the rule. Then you can see exact where it goes wrong. The result will be shown in the audit log. See image below for examples.
You must expect many "No actions performed" in the audit log, because any time an issue in the rule scope is transitioned from To Do to In progress the rule will be triggered, and every time that trigger "leads to nothing" (e.g. in this case for a non-subtaks) "No actions performed" will be set.
I will also suggest you early in a rule add a filter for which issues you want to target. In your scenario it is all subtasks and only subtasks. So you might apply something I shown in the image.
Hi @jonathan.wiebe, here is an example of a rule if it is Epic as parent you are looking for, and not parent of sub-tasks.
Notice, as @Trudy Claspill states in the comment, the brancing is Epic (parent) for this scenario.
You don't need the filter Issue Type equals Epic after the branching, because only Epics will enter this branch, hence it's already "filtered".