Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to sync issue links

This article is about how to configure Exalate such that issue links between jira issues on the source get recreated in the target.



For instance assume on the source you have AAA-123  linked with DDD-234 using a 'relates to' link type.

Assume now that the synced issue of AAA-123 becomes XXX-345 on target, and the synced issue of DDD-234  becomes YYY-456.  How can Exalate be setup such that XXX-345 is automatically linked with YYY-456 using the 'relates to' link type?



Issue link synchronisation is an out of the box feature of Exalate.  

First of all, you need to ensure that the issue link information is sent over to the target by adding to the outgoing message processor 


// Add the issue links to the message
replica.issueLinks = issue.issueLinks


On the target side, add to the incoming message processor


// automatically apply the same links to the twin

issue.issueLinks = replica.issueLinks


That's it - Simple as Bonjour.


More information


Here is a video showing how it works
Issue sync - respect the issue links


The documentation page specifying how to configure this type of synchronization

Do you want to know more, feel free to book a demo


In a next article, I will explain how you can automatically link synced issues.




This is not working, I've tested it out and it's not working, also the new docs suggest to do a different thing:, but that solution only works for creating the issues, it doesn't work when updating them, I've raised a support ticket on their system to get an answer, maybe if you're part of the team you could help.

francis Marketplace Partner Oct 03, 2019

Hi Jo,


I'm part of the team.


What do you mean by 'updating the link'?


PS - we can continue the discussion here, or if on the support ticket you raised on our community site. The latter has the benefit that the people who are using Exalate can benefit from the conclusions, while this blog location is remote to it.



Let's switch to exalate community, I added more detail there.


Log in or Sign up to comment

Atlassian Community Events