This use case describes how you can synchronize Jira issues bidirectionally between two projects. This can be helpful when you want to:
-
Synchronize your issue data with a partner and you both want to make updates to the work items .
-
Synchronize issue data with another project on the same Jira instance because some issues are affecting both projects.
With a bidirectional synchronization you can have the same data on both sides. Backbone detects each existing issue from your project(s) and creates a new issue with the same data in the other project. Afterwards, each change synchronizes between both issues.
Configuration guide
In this guide, we will configure a Jira project so it synchronizes issues with another project bidirectionally. This guide assumes the other project already exists.
-
Create a new synchronization between both projects.
-
Configure Issue Type Mappings and Field Mappings and make sure they are bidirectional (this is the default).
Congratulations! The basic configuration is now complete. You can now add Attachment , Comment or Workflow Mappings if desired.
Good to know
-
Backbone must be installed and licensed on both sides.
-
Only the configured fields will synchronize - so you can keep some fields secret.
-
Do you want to synchronize only a limited set of issues? You can limit the issues in the issue type mappings .
-
Not all mappings have to be bidirectional, you can also combine bidirectional and unidirectional mappings.