Trying to diagnose "No Actions Performed" on Automation that should transition a parent issue
Asked by jonathan.wiebe:

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?

![image.png](/t5/image/serverpage/image-id/286051iDDCBFA53E392D988/image-size/large?v=v2&px=999 "image.png")


Answers:
author: Trudy Claspill
body: Hello [@jonathan.wiebe](/t5/user/viewprofilepage/user-id/2716597)

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.

![Screenshot 2023-10-12 at 3.25.59 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/286058i19ED6E01A79652A3/image-size/large?v=v2&px=999 "Screenshot 2023-10-12 at 3.25.59 PM.png")

comments: author: jonathan.wiebe
body: ![Screenshot 2023-10-15 214456.png](https://community.atlassian.com/t5/image/serverpage/image-id/286415i36E21EFC77848752/image-size/large?v=v2&px=999 "Screenshot 2023-10-15 214456.png")

Added issue types, but haven't had a chance to test this new configuration.


author: Trudy Claspill
body: 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.


author: jonathan.wiebe
body: Ah, I see. I hadn't noticed the "Epic (parent)" option before. I've made the change and hope to have a chance to test soon.


author: Tim Kopperud
body: Hi [@jonathan.wiebe](/t5/user/viewprofilepage/user-id/2716597)

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.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/286106iB6D33F6B45FBA6BE/image-size/large?v=v2&px=999 "image.png")

TimK.

comments: author: Tim Kopperud
body: Hi [@jonathan.wiebe](/t5/user/viewprofilepage/user-id/2716597), 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](/t5/user/viewprofilepage/user-id/3569011) 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".

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/286439i7AA6F7281DCE9BFF/image-size/large?v=v2&px=999 "image.png")

TimK.


author: jonathan.wiebe
body: This makes sense, now that I've discovered the "Epic (parent)" branching option. Hope to test soon. Thanks for the tip and screenshot!


author: jonathan.wiebe
body: I can confirm that this automation now works as intended! Thanks [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) and [@Tim Kopperud](/t5/user/viewprofilepage/user-id/492874)! Much appreciated!


Tags: cloud

jira-work-management-cloud