Unidirectional Synchronization

• Provide information about your Jira work items to a partner but only want them to view information without synchronizing updates back into your Jira.

• Stay informed of work items of another project your work depends on, but don't want to expose your updates to them.

With a unidirectional synchronization, Backbone detects every change in the source project and synchronizes it over to the target project - ensuring everyone is up to date. You stay in control of your data and configure exactly what kind of information is exchanged.

Configuration Guide

This guide shows you how to configure a unidirectional synchronization.

1. Create a Synchronization between your project and the project of your partner.

2. Configure unidirectional issue type mapping.

3. Configure unidirectional field mappings.

Congratulations! The basic configuration is now complete. You can now add unidirectional attachment, comment or workflow mappings if desired.

Good to know

• Not all mappings have to be unidirectional. You could also decide to synchronize fields unidirectionally and comments bidirectionally.

• In order to avoid configuration errors, you can restrict the permissions of the synchronization user in the source project so Backbone is not able to create or edit issues at all.

• Backbone must be installed and licensed on both sides. Not possible? Learn about our remote licenses.