JIRA SERVER

Disclaimer

 

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 sales@exalate.com for more information.

 

This page describes how to synchronize an agile project  It means that all agile information within the project (sprints, epics, issues with all data including issue key, change history, issue links, sub-tasks, typical issue custom fields, etc) will be synchronized.

Pre-requisites: 

  • 2 Jira Server instances: sending and receiving
  • 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.
  • Instance created on RED Jira
  • Instance created on BLUE Jira 

Description:

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. 

Connection Configuration

Let's consider you already have the Connection created on both Jiras. Now you need to customize synchronization processors with the 

  1. Configure Sync Rules with the appropriate scripts provided below. 

    Attention!

    We provide scripts for demonstration purposes. Every script needs to be adapted for your specific use case.

    Scripts for sending side

    (JIRA Server)

    Scripts for receiving side

    (JIRA Server)
    Data FilterData Filter
    Create ProcessorCreate Processor
    Change ProcessorChange Processor

    Every script includes comments. Please be sure to follow the instructions from the script's comments. It is important for the successful synchronization.

    (Version: 1.0.0-rc2)

  2. 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.

  3. 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 migrate issue using the Exalate app.