Skip to main content
Skip table of contents

Synchronize with changing Jiras

This use case describes how you can synchronize Jira issues with Jira instances that change from time to time. This can be helpful when you want to:

  • Synchronize a Jira project with a customer's Jira project for a limited amount of time

With Backbone, you can synchronize your projects with another Jira without installing anything on their end. Instead, you install a Backbone remote license in your Jira and then synchronize projects with the other Jira. When you are done synchronizing projects with this Jira, you can reuse the license for synchronizing with another Jira.

Configuration guide

This guide explains how you can synchronize your Jira with Jira A and later then with Jira B.

  1. Install Backbone from the Atlassian Marketplace in your Jira and get a usual (trial) license.
  2. Contact K15t to get a (trial) remote license and tell us how many Jiras you want to synchronize at the same time. We'll then send you a trial remote license.
  3. Install the remote license in your Jira.
  4. Create a new synchronization with Jira A and configure the synchronization details.
  5. When you no longer need to synchronize with Jira A, stop all synchronizations with Jira A.
  6. Create a new synchronization with Jira B and configure the synchronization details.

Congratulations! The basic configuration is now complete. You can now configure additional issue types, fieldsattachmentcomment or workflow mappings if desired.

Good to know

  • You can have multiple synchronizations as long as they synchronize issues with the same Jira instance to which the remote license applies.
  • If you no longer have any running synchronizations with one external Jira, you can repurpose the remote license to synchronize with another.
  • The Jira instance where Backbone is configured must be a Jira Server or Data Center.
  • The Jira instance without the Backbone installation will not show a Sync Info Panel.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.