To be able to develop advanced synchronization scripts you require a development background and a good understanding of Groovy and the entities of the underlying issue tracker and Exalate itself.
In case of need, we can provide training and professional services to deliver the solution you're looking for. Please contact email@example.com for more information.
This page describes how to synchronize a simple project. It means that all information within the project (issue key, change history, issue links, sub-tasks, typical issue custom fields, etc) will be synchronized.
The scripts below work also for sprint synchronization on Jira Server.
- 2 Jira Server instances: sending and receiving
- A project with data on the sending side (RED Jira): Project Tasks (PT)
- An empty project on the receiving side (BLUE Jira): Project Tasks (SD)
- A connection setup between the two JIRA servers
Script Rule configuration
We provide scripts for demonstration purposes. Every script needs to be adapted for your specific use case.
Now you need to customize synchronization processors as follows
Scripts for sending side
Scripts for receiving side
|Data Filter||Data Filter|
|Create Processor||Create Processor|
|Change Processor||Change Processor|
For Exalate 4.3
- Create a Trigger on the sending side:
In the add-on section of your Jira, access the triggers and create a new trigger. Include all issues in your project to be synchronized using the previously created relation. The relation towards the receiving instance ( BLUE Jira). Activate the trigger.
- Use Bulk Exalate to synchronize multiple issues at a time.
Exalate is running through all the issues and sending out all the information from the BLUE instance to the RED instance.
After a while, all issues will be showing up in the same configuration as on the RED instance.