Automation: Linking and transitioning duplicates not working

[Sebastian Pechhold]

Hey community,

i want to give issue B a specific status if it is a duplicate from issue A.

Issue B is the new issue, and issue A already exists.

1. open issue B
2. link to issue A by "duplicates" or "is duplicated by"
3. current state: issue A is "declined"
4. target state: issue B is "declined"

Already tried this.

[Mark Segall · Accepted solution]

Hi @Sebastian Pechhold The most important thing to understand about the Issue Linked trigger is how the source/destination work:

Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

Your ask:

i want to give issue B a specific status if it is a duplicate from issue A.

Tying your case to the explanation above, issue A is duplicated by Issue B.  Therefore Issue B  is {{issue}} and issue A is {{destinationIssue}}

Now that we have this down, if I'm understanding correctly, you want to transition the duplicate ({{issue}}) to Declined.  Your rule would look like this:

• TRIGGER: Issue Linked (Duplicate)
• ACTION: Transition Issue (To Declined)

This would be a single rule because Jira automation has no mechanism for determining which issue initiated the linking.  It always bases off of the link relationship.

I hope this makes sense.

[Sebastian Pechhold]

Hi Mark, we found out that we have to use Issue A and link issue B to it.

That works because issue B gets declined as "duplicate(s)"