Issue Linked Trigger only triggers in one direction

Jack Zgierski April 17, 2024

The Issue Linked Trigger only catches 50% of link events. It only triggers when the 'source issue' is linked to the 'destination issue'. When 'destination issue' (from another project) is linked to the 'source issue' of course the automation rule is NOT triggered because the automation does not exist in the 'destination issue' project.

This is completely useless because the reality is that two issue are being linked! Automations should trigger in BOTH projects for BOTH 'source issues' and BOTH 'destination issues'

ex. I have PROJA-11 linking to PROJB-12. Automation Rule should trigger in PROJA IRRESPECTIVE of whether

1) PROJA-11 is linked to PROJB-12
2) PROJB-12 is linked to PROJA-11 

as it is only #1 triggers the rule but not #2 - this is wrong.

Any solution around this serious bug which renders the Issue Linked Trigger useless?

1 answer

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2024

Hello @Jack Zgierski 

On the Rule Details page for the rule change the Scope to Multiple projects. Then in the Projects field select all the projects that could have issues involved in the link process you're trying to to capture.

Note that you'll have to go to the Global Automations page to make that change.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events