This article describes how to sync issue links between JIRA Server Instances.
Source Instance
Send over the issue links
Outgoing sync
replica.issueLinks = issue.issueLinks
Destination Instance
Add the script below in the Incoming sync of the Destination instance to receive issue links from the Source Instance.
Incoming sync
issue.issueLinks = replica.issueLinks
Warning: You should separately synchronize all issues that are linked to a specific issue to keep an association between them on the Destination side.
Sync between projects DEV and TEST;
issue DEV-1 is linked to issue DEV-2;
sync issue DEV-1 to TEST-1;
TEST-1 still is not associated with any other issue
sync issue DEV-2 to TEST-2;
as a result, you get a link between remote issues on the TEST project (TEST-1 and TEST-2)
- The default issue links synchronization behavior does not include merging issue links from the source and destination issues. Once the issue has been synchronized, it has the same links as the source issue.
- If you sync the issue via multiple connections, issue links are overwritten.
Note: In case you don't want the source issue links to be overridden if the remote side doesn't have any issue links we recommend using the external script IssueLinks.groovy.
See it in Action!