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 firstname.lastname@example.org for more information.
This article includes groovy scripts that help to synchronize sprints on Jira Cloud in a unidirectional manner.
Synchronizing sprints means all sprint information will be exchanged between two instances.
- 2 Jira Cloud instances: BLUE and RED
- A project with data on the sending side (RED Jira): scrumdemo (SD)
- An empty project on the receiving side (BLUE Jira): scrumdemo (SD)
- An empty board on the receiving side. The board should have the same name as on the sending side.
- Connections configured on BLUE and RED Jiras.
We have a BLUE Jira and a RED Jira. RED Jira has the project that needs to be synchronized to BLUE Jira. BLUE Jira has an empty project to receive data from RED Jira.
Both projects have the same name scrumdemo, same key SD, and the same user submit.
Sync Rules Configuration
Let's consider you already have Connections created on both Jiras. Now you need to configure Sync Rules scripts.
Configure Sync Rules on both sides (source and destination).
Configure synchronization processors with the appropriate scripts provided below.
We provide scripts for demonstration purposes. Every script needs to be adapted for your specific use case.
Scripts for sending side
Scripts for receiving side
Data Filter Data Filter Create Processor Create Processor Change Processor
Every script includes comments. Please be sure to follow the instructions from the script's comments. It is important for the successful synchronization.
- 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 connection. The connection 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.
Congratulations! Now you know how to sync an agile project using Exalate.
Sub-task synchronization requires additional scripting.
If you have subtasks in the project you are synchronizing, please contact us at email@example.com for more details.