In this article, we describe how to synchronize Epics, including Epic link.
Requires Exalate for Jira Server/DataCenter version 4.5.1 or higher
With Exalate, you can sync epics and stories, while keeping the parent-child relationship on the remote side.
To keep parent-child relation between issues, you need to synchronize Epics first, then synchronize stories.
After you establish a connection between two Jira instances, you need to configure the Sync Rules.
The script works only when using scripting rules on Jira Cloud. It's not compatible with Exalate visual mode.
You can only map Epic name custom field in visual mode.
To sync epics in Jira Server:
Create files from the Exalate public repository.We store external scripts for Jira Server in a public repository. Copy the code from the repositories below and create .groovy files. You must keep the filenames as below.
Note that you will need to disable/enable the Exalate add-on such that the new file is added to the classpath.
Upload the files to
$JIRA_HOME/scriptsdirectory is located on the server, where you have your Jira instance installed.
If you don't have a scripts directory you should create it. Check out How to add an external script in Jira Server for more information.
Configure Sync Rules with the scripts provided below:
Add the code from the repository accordingly into the bottom of the Sync Rules.
Add the following code to send the Epic information together with the Epic Link.
You need to synchronize Epic first, then synchronize stories to keep parent-child relation between issues.
This example shows the case where the order does not matter, still keeping the parent-child relation between Epic and Stories. The Epic Link will be also synchronized.
Add the following code to apply received Epic information, including the Epic Link