{{announcement.body}}
{{announcement.title}}

Synchronization of Jira Projects Between 2 Jira Instances

DZone 's Guide to

Synchronization of Jira Projects Between 2 Jira Instances

In this article, we will see how to address a collaboration challenge between projects in Jira and the options available as a solution.

· Agile Zone ·
Free Resource

Introduction:

Most of us are aware that JIRA is one of the best application lifecycle management tools on the market. The main feature of Jira is team collaboration. We may come across a situation where there is a challenge in collaboration between the business team and partners due to their network restrictions.

In this article, we will see how this problem will be addressed and what are all the options available as a solution.

Business Case:

In many IT projects, the service provider may not get direct access to the customer environment or tools, it will be challenging to collaborate effectively with the customer. To overcome this problem Jira has given a mirror kind of synchronization option between 2 instances in different networks. Let's see how to achieve that connection in this article.  

Available Solutions:

Many vendors addressed this problem and introduced their solutions in the form of automatic synchronization as a Jira plugin.

 Some of those Jira plugins are,

In this article, we’ll take Backbone Issue Sync and see how the synchronization of Jira projects will be done between 2 Jira instances.

Backbone Issue Sync

Backbone Issue Sync helps us to synchronize your JIRA projects and letting us collaborate across departmental and B2B borders.

The setup and configuration also very simple compared to other plugins.

Backbone issue sync is developed by K15t group available in Atlassian market place and it is a paid plugin

This plugin support following Jira versions

  • Jira Cloud
  • Jira Server from 6.2 – 8.6.1

Jira Data Center 6.3 – 8.6.1

 

Pre-Requisite:

  • Jira to be installed in both the side (Customer & Vendor)
  • Create a Jira project with the same name in both Jira instance
  • Create a Jira user named “syncuser” on both the instance

Syncuser has to be Granted Jira permission to Browse Projects, Create Issues, and Edit Issues.

Diagrammatic Representation:

 bi directional synchronization between jira instances

Establish a Connection Between the Projects

1. To start with open the Jira Project in Instance1 then select Project settings > Issue Synchronization > New Synchronization. To make things very simple, select Centralized Configuration (this is Backbone's 'default' synchronization type, and is recommended for most of the use cases).

2. Now, you can start setting up the synchronization,

a. In Base URL, enter the Base URL of your Jira in First Instance and Base URL of external partner’s JIRA URL in Second Instance

b. In Synchronization, Users enter the synchronization user's username (in this example, that's syncuser).

c. In the Password field, enter the synchronization user's password.

3. On the next screen, select which project you want to synchronize with. Select the same project name in both the instance

4. Next, you can assign the synchronization a name and description. when you create multiple synchronizations for a Jira project, descriptive naming is important to avoid confusion. For now, we will go with the default values.

We have established the connection between Jira projects of 2 different instances! Now, let's configure what are all the data will be synchronized between the projects of each instance.

Configure synchronization settings

1. In the below step, we'll configure the synchronization data, telling Backbone what data it should synchronize between the projects of 2 instances.

2. Click ... > Configure to go to the configuration UI:

3. Click the Edit Configuration button to start configuring.

4. On the Issue Types tab, click Start with simple mappings and select an issue type to synchronize in both directions between 2 instances of Jira projects.

5. Now, map which fields should be synchronized at Fields - Mappings > Start with simple mappings.

    a. Enable the checkbox for the Summary and Description field and then click Create.

    b. Then click the Publish Draft button to save the configuration, then select Start to start the synchronization.

That’s all we have configured the synchronization with Backbone Issue Sync. 

Let’s Verify the Synchronization

1. Create a new issue with type Task in first Jira instance, and enter some content in the Summary and Description fields.

2. Now, open the Jira Project in second Jira instance – you'll see that the issue has now been synchronized.

3. Open the synchronized issue and edit the summary and description in the second instance.

4. Go back to the issue in the first Jira instance, and can see the edits been synchronized back over.

Conclusion: 

Backbone issue sync helps us to overcome the challenge of collaboration over the restricted security network between customer and external partners. Many highly secured business teams are now relieved from this problem and established smooth collaboration through Jira and Backbone issue sync.

Topics:
agile adoption, jira, jira add-ons, jira api, jira resource management

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}