Link Type Automation Won't Trigger

[Brad Hebert]

I've attempted to setup an automation to add a label to an issue when there is a specific link-type is present. No matter how I configure the automation, it never seems to trigger or identify any issue as an eligible issue for the automation.

Just looking for any pointers that can be offered here as the "If Linked Issues Present: Link Type" does not seem to catch any tickets created with the link type. I've also created a version of this automation that should trigger based on the issue being updated and even in that configuration an issue linked with the desired link-type still does not end up being labelled or triggering the automation rule.

[Bill Sheboy]

Hi @Brad Hebert -- Welcome to the Atlassian Community!

There are two possible causes for this symptom...

First, the Issue Created trigger can fire so quickly that some data is not yet available to the rule.  As linking happens after issue creation, it is likely the data is missing when that condition is attempted by the rule.  The "fix" for this is to always add the Re-fetch Issue action after the Issue Created trigger.  This will slow the rule down a bit and reload the information before the rule proceeds.

Second, most issue links are directional, such as "blocks" and "is blocked by".  If your link type has direction and the wrong one is selected, the condition would never pass.  Please check your links and update the condition, as needed.

Kind regards,
Bill

[Mohammed Shakhib]

Hi everyone,

Due to the age of this thread, it has been closed to further replies. Please feel free to start a new thread if you wish to continue to discuss this topic.

Thank you for understanding.

[Darryl Lee]

Ohey @Brad Hebert and @Bill Sheboy - funny, I'm working on an automation and running into the same issue.

I did some testing and I've added the following to the audit log before my conditional check for "Linked issues present (Types: All link types)".

Lo and behold, logs show:

links: SUS-4860

But the subsequent "CONDITION FOUND LINK" message never shows up:

This feels like a bug. I guess we could work around it by using a smart value comparison like checking if this is true:

{{issue.issueLinks.isEmpty}}

But ugh. Why have a condition if it doesn't work? I'm gonna file a ticket.

[Darryl Lee]

Ugh, I figured it out, and it's annoying because it's right there:

Sigh. Welp, thanks for helping me rubber duck my problem. I don't know if it helps with your issue @Brad Hebert .

[József Porohnavec]

Hi,

I encountered the same issue, but I still believe it's an Atlassian bug, as the automation runs successfully without specifying a link type. However, when I specify either the inward or outward link to narrow down the condition, it just does not run.

Shouldn't be a race condition as the Related issues condition returns true without specifying a link type, so the linked issues are detected, but it seems to be the case, as adding the Re-fetch Issue action just before the step solves it. 🤷‍♂️ At least evaluating one conditional step should be atomic...