Cloned tickets Linked Issues integration

[Jagoda Zawadzka]

Hi,

I have two issues: SD-41 (main issue) and DEL-1031 (cloned by SD-41 while SD-41 creation).

I need to fully integrate both of those so that if fields in SD change, the same fields change in DEL (and the other way as well).

I've found this article: https://community.atlassian.com/t5/Jira-Software-questions/Update-cloned-issues-simultaneously/qaq-p/1028691 and I was able to integrate (almost) everything.

The biggest challenge I have is with integrating Linked Issues in between these two.

I want to create a rule so that if any issues are linked to any of the tickets, the other one updates with the exact same links.

I created a below automation:

From the Audit Log, I'm seeing No Actions Performed as it seems that the issues taken into consideration are not the ones that are cloned but the ones that are linked to the cloned issue.

I tried changing the rule (copy from triggerr rule, destination rule, changed linkn type, etc.) but nothing seems to work.

Are you able to help me?

Thank you in advance,

Jagoda

[Matthias Gaiser _K15t_]

Hey Jagoda,

welcome to Atlassian's community.

Automation

I tried to follow your setup and ran into the same problem. I got No Actions Performed as well. I think, I've figured out the reason for this. It seems there is a difference if you link on the screen of issue A-1 to A-2 vs. on the screen of issue A-2 to A-1.

Issue linked

Source issue (the main branch of the rule will execute for this issue and you can access it via {{issue}}):

ATP-80

Destination issue (to perform actions on this issue use a 'Related branch', you can also access it via {{destinationIssue}}):

ATP-21

You will see an output like the one above in your audit.log - and depending on the direction, the source and destination issue will change.

In order to workaround that, you'd probably need to not copy the values for the issue links, but rather add the newly linked issue via the "More options" so that you can conside the link type and add the correct issue key.

Issue Sync

As Dhiren said, another way would be to use an issue sync solution. I'm part of the team behind Backbone Issue Sync and I know that you'd be able to configure synchronizing issue links without going that deep into the configuration.

Cheers,
Matthias.

[Dhiren Notani_Exalate_]

Hi @Jagoda Zawadzka

Thanks for posting your question here!

Can you please elaborate a little bit on the Use-Case here?

If you are looking for a bi-directional synchronization between both the Jira Issues then I would recommend you to use an integration solution like Exalate

With the no-code mode, you can start integrating in less than 10 mins. For solving the most challenging use-cases and for ultimate level of customizations, Exalate also offers a scripting mode which is based on Groovy. 

I work for team Exalate. Please feel free to ask any questions if you need further guidance.

Hope it helps. 

Thanks, Dhiren