This use case describes how you can synchronize Jira issues between firewall protected Jiras. This can be helpful when you want to:

  • Synchronize Jira issues with a partner, but both Jiras are protected by firewalls so they can't reach each other via HTTP(S).
  • Synchronize Jira issues between two Jiras which are physically disconnected, e.g. due to specific classification levels.

With Backbone's distributed configuration, you can synchronize Jira issues and work around firewall issues. You can choose from two options, depending on how you want to exchange data between the two Jiras:

  • File-based. Backbone exports all changes to the file system - these files can then be exchanged as you wish, via network folders or pen drives.
  • Email-based. Backbone on Jira A sends all changes via mail to Jira B, and vice versa.

If one Jira can reach the other Jira directly via HTTPS or you can define a firewall exception to allow that, we recommend you do so. This simplifies the configuration of Backbone a lot. You can then choose from the other use cases to proceed, e.g. Bidirectional synchronization.

Configuration guide

In this guide, you will configure a synchronization using the distributed configuration approach. This enables the Jiras to exchange issue updates via email or files. This guide assumes the other project already exists.

  1. Make yourself familiar with the concept of a distributed configuration.
  2. Create a new master synchronization in Jira A. In this step, you select whether you want to use the mail- or file-based exchange. After the creation you can download a handshake file with all important information to create the slave synchronization.
  3. Create a new slave synchronization in Jira B. Use the handshake file from step 2 to create it. After this step, the master and slave synchronization status switch to stopped.
  4. Configure some issue type and field mappings in the master synchronization. After adding the mappings, publish them so the slave receives the configuration update.
  5. Complete the configuration of the added mappings in the slave synchronization.

Congratulations! The basic configuration is now complete. You can now add AttachmentComment or Workflow Mappings if desired.

Good to know

  • Backbone must be installed and licensed on both sides. Read more about licenses.
  • The full feature set of Backbone is supported in this use case. However, for each configuration side (master or slave) you can only configure that specific side. The mapping between both sides is done using common identifiers, e.g. a message alias for the field mappings.