Why the parent issue isn't find in my automation rule ?

[Raphaël NORYNBERG]

Hi everyone,

So basically my case is the following, I want to transition parent issues when all their childs meet a certain status.

I made an automation rule that triggers whenever a subtask do a precise transition, then a branch "For: Parent", I added some conditions then the action "Transition".

But when the rule triggers, it says this :

Branch rule / related issues

No related issues could be found.

I don't get why... when I search with JQL the parent issue of my subtask is found

Could someone help me to understand and make this works ?

Thanks in advance

[Sarp Egemen · Accepted solution]

Hi @Raphaël NORYNBERG 

I replicated your automation in my environment, and it works.

I will break down your automation into steps so you may find something you didn't intend to do.

--------

First, your rule will only run for an issue that transitions from "en cours de dev" to "documentation à rédiger."

(Let's say we have an issue named "my issue" that undergoes the transition mentioned above.)

First of all, this issue must have a parent for the rest of the rule to execute. Therefore, this issue must be of either task level or sub-task level.

(Let's assume there is an epic called "my epic" that has "my issue" as a child.)

Then, the rule checks the parent of "my issue" which in this case is "my epic," and runs the conditional on that epic.

If "my epic" has a type of "Use Case" and a status of "En attente composant," then it looks for the second condition.

If "my epic" has subtasks, and all of those subtasks are of type "Composant" and are in any of the statuses "Rejeté", "Documents à rédiger" or "Traité"

Then "my epic" gets transitioned to "à prioriser."

[Raphaël NORYNBERG]

Hi @Sarp Egemen thanks for your reply,

In my case the issue that triggers the rule is a "sub-task level" and it has a "task level" parent (which does appears like this in JQL search).

And yes I have double checked that conditions are met.

[Raphaël NORYNBERG]

@Sarp Egemen  @Tobias H Sorry I was obviously tired yesterday, it all works fine, I have mistaken with an old issue type ("Use case" wasn't my type it was "Use cases" ...)

[Tobias H]

Oh such a simple mistake to make, great that you found it once you had gotten some sleep in! :D

[Sarp Egemen]

It happens to all of us. ✌🏻 Glad you figured it out. 

For me, especially when I get stuck on a problem and feel overwhelmed, taking a break and then returning to it really helps me see things I've missed. 

[Tobias H]

Hi @Raphaël NORYNBERG! 

Just to get some more info, is there only one subtask attached to the parent? As the "related issues" component checks all subtasks for their status and type.

Also, have you tried adding a re-fetch after the trigger? That might give the automation enough time to find that the parent's subtask actually has transitioned.

[Tobias H]

I just copied your automation (and added an if statement for which project)

And it ran just fine, so I'm also a bit perplexed now 😅

[Raphaël NORYNBERG]

Hi @Tobias H , thanks for your reply,

I'm going to try that re-fetch after trigger thanks.

And yes there is multiple subtasks but they all meet the status conditions.