Automation: Branch "For Epic (parent)" isn't executing actions

[Deleted user]

In a system-managed "next-gen" project (Classic projects are unavailable in my instance), I am unable to get the "For Epic (parent)" branch component to work properly.

I have some epic, FOO-1. Within it, there is a single issue, FOO-2 with an Epic Link back to FOO-1.

FOO-1 is currently "Open", and has a valid transition path to "Closed".

Transitioning FOO-2 to Closed should be closing FOO-1, as it is the only issue in the epic and has a status of "Closed" -- however, this does not occur. In testing (adding actions for commenting, email under the branch), it appears that the "For Epic (parent)" branch condition is not functioning correctly. There is not an error in the audit log; there is simply a status for runs of "No Actions Performed".

Is anyone else experiencing this, and have you found any workarounds? I found a few issues that seem to indicate that the Epic Link is implemented differently as of a few years ago, but I haven't found any concrete issue that indicates this is a known bug.

[Deleted user · Accepted solution]

This has auto-resolved, magically, without any sort of configuration changes at either the rule, project, or system level. This leads me to believe that there was some sort of backend issue with our instance that has been resolved.

[Garrett McCreery]

You could try using branch rule "For JQL" and then use the JQL query listed. 

[Deleted user]

That function is only available to Jira Premium accounts, which we do not have at the moment.

[Garrett McCreery]

How about this:

get the parent (which is the epic):

Then use the JQL branch method:

[Jack Brickey]

Hi @[deleted] , welcome to the Community. First I wanted to clarify that in TMP (next-gen) there is not an Epic link that is unique to CMP (classic). That aside, could you share the audit log here?

[Deleted user]

I'm not sure what new information the Audit Log would provide. Unless there's something I'm not seeing, all it contains is the issue that triggered it, and then a status of "No Actions Performed".

[Jack Brickey]

Hmmm, it doesn't provide a reason?

[Jack Brickey]

@[deleted] , FWIW I replicated your rule and tested it successfully in my instance. I had a test epic with two stories. I closed the first story and verified that the rule exited on the condition that all associated stories were done. I then transitioned the second story to done and the epic was transition to done by the automation rule. 

One thing to note is that my audit log indeed provided the necessary information. So there's something odd if your audit log is not giving a clue. At least it seems that way on the surface. The thing I'm most interested in is which step in the rule does the automation exit on?

[Deleted user]

It fails because no issues match the "For Epic (parent)" branch condition.

[Deleted user]

[Jack Brickey]

maybe try to setup a new test ?

1. create an epic
2. create two children under the epic
3. close one and inspect audit log
4. close the second story and inspect audit log

[Deleted user]

Yep, I did that before opening this issue and things worked just fine.

This has now been resolved, because the rules have started working, magically. No configuration changes were made at either the rule, project, or system level. This leads me to make the assumption that something was happening with the backend that has now been resolved.