Preventing duplicated issue links

[Renee Tibedeau]

How do I prevent duplicate links from being created when automation is setup to clone multiple tickets?

I have automation setup for when a specific ticket is created to clone several additional tickets with varying summaries and labels being added. I have the cloned tickets setup to create a link to the trigger issue. The problem I'm having is that I'm getting 2 links for each cloned ticket rather than 1. 

Automation setup:

Current links created: 

PC-225 A: test

PC-226 B: test

PC-226 B: test

PC-227 C: test

PC-227 C: test

PC-228 D: test

PC-228 D: test

Links needed:

PC-225 A: test

PC-226 B: test

PC-227 C: test

PC-228 D: test

[Trudy Claspill]

Hello @Renee Tibedeau 

Can you show us the details of the actions that are creating the second, third, and fourth issues?

Do you have any other rules active for the project that are triggered by issue creation?

[Renee Tibedeau]

The second, third and fourth are the same as the first other than a different summary and labels being added. Here is the second for reference: 

I should have sent this with my original post and missed it. This is the rule I have for copying links:

Additional rule I have setup to populate a custom field with panels on ticket creation.

[Trudy Claspill]

For the Relays link, what is the Outward Description and what is the Inward Description?

I'm pretty sure that the duplicate links have something to do with the fact that in the first rule where you create the issues you are creating a Relays link, and then you have a second rule that that is copying the Relays link after it is created.

[Renee Tibedeau]

Outward and inward have the same description "relay to relay with". I am copying the links so that each of the tickets can easily navigate to any of the linked tickets. In the below example if I was in ticket 226 I could then navigate directly to 225, 227 or 228 rather than having to go to 227 to get the link for 228 etc.

Links needed:

PC-225 A: test

PC-226 B: test

PC-227 C: test

PC-228 D: test

[Trudy Claspill]

Using the Issue Linked trigger is a little tricky. 

I recommend that you add Log Actions to the Copy Links rule to trace which issues are being looked at in any given moment.

After the Trigger element, I would add a Log Action and log the triggerIssue.ID so you can see for which issue the rule is running.

In the Branch I would add Log Actions to log the triggerIssue.ID again, and the issue.ID so you can confirm which two issues are being compared.

There might also be a timing issue between when the issues are cloned and linked in the first rule and when the Copy Links rule is triggered. If the Copy Links issue is triggered for the first copied issue right after that issue is created, then the second/third/fourth issues don't exist yet and the first issue can't get links to them copied to it by copying links from the original issue.