This use case describes how you can synchronize Jira issues unidirectional between two projects. This can be helpful when you want to:

  • Provide information about your Jira issues to a partner but only want them to view information without synchronizing modifications back into your Jira.
  • Stay informed of issues of another project your work depends on, but don't want to expose your adaptations 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 Mappings.
  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.