Backbone Issue Sync allows you to integrate two Jira projects to synchronize issues.
Scope of a synchronization
Synchronizations are always configured on a project-by-project basis, always between two projects.
However, you can create multiple synchronizations per project. So if you want to connect one project with multiple projects, you can simply create multiple synchronizations for a project.
Data transmission protocol
Backbone uses the official Jira REST API in order to access both Jira projects which it integrates. If you provide a HTTPS URL when you setup the synchronization, Backbone will use an encrypted channel in order to communicate with JIRA.
You can create new JIRA project synchronizations using two different configuration types – either distributed configurations or centralized configurations.
This article will explain which configuration type you should select depending on your use case.
You should use a centralized configuration if:
Your Jira can reach the other Jira directly via HTTPS or vice versa
- You want all administration tasks to be carried out in a single JIRA instance
- You have already successfully used the centralized method with a particular partner and want to use it again
If your requirements match these criteria, please create a centralized synchronization.
You should use a distributed configuration if:
- Both JIRA instances are behind a firewall and no Jira can connect to the other via HTTPS
- One or both project owners might want to hide JIRA config information (e.g. issue type/field/workflow status names) from the other
If your requirements match these criteria, please read more about distributed the distributed configuration and create a distributed synchronization.
In general, we recommend to use the centralized configuration since this is easier to administer.