JIRA CLOUD JIRA SERVER
This article includes groovy scripts that help to synchronize sprints from Jira Server to Jira Cloud.
Synchronizing sprints means all sprint information will be exchanged between two instances.
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.
- Jira Server Instance
- Jira Cloud Instance
- A project with data on the source side: Jira Server
- An empty project on the destination side: Jira Cloud
- An empty board on the receiving side. The board should have the same name as on the sending side.
- Connection configured between Server Jira and Cloud Jira.
We have a Jira Server and a Jira Cloud. The Jira Server has the project that needs to synchronize with the Jira Cloud. The Cloud Jira has an empty project to receive data from the Server Jira.
Both projects have the same name, same key, and the same user submit.
This configuration helps to synchronize sprints from the Server side to the Cloud side.
Let's consider you already have the connection configured between Server and Cloud JIRA instances. Now you need to configure Sync Rules.
Configure Sync Rules' scripts on both sides (source and destination).
Synchronization processors should be configured with the appropriate scripts provided below.
We provide scripts for demonstration purposes. Every script needs to be adapted for your specific use case.
Jira Server (source side)
Jira Cloud (destination 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 (JIRA Server). 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 Jira Server instance to the Jira Cloud instance. After a while, all issues will be showing up in the same configuration as on the source instance.
Congratulations! Now you know how to sync sprint using Exalate.
If you want to use this script, but you are missing a functionality or would like to get it adapted to your use case, contact us at https://support.idalko.com.