Backbone has multiple features that make synchronizing issues flexible and powerful.

Control what's synchronized, and in what direction

Backbone supports unidirectional and bidirectional synchronization of Jira issues. You stay in control which information will be shared.

If you want to limit which issues are being synchronized, you can define a JQL filter to select a subset of issues.

In addition to filtering on the issue level, you can also decide which fields should be synchronized, so you can keep some fields internal.

Backbone supports the synchronization of many Jira features like:

Check the field mappings page for more fields.

Support for all Jira deployments and applications

Backbone lets you synchronize issues between all kind of JIRA deployments:

Jira ServerJira CloudJira Data Center
Jira Server(tick)(tick)(tick)
Jira Cloud(tick)(tick)(tick)
Jira Data Center(tick)(tick)(tick)

And the following Jira applications:   

  • Jira Software
  • Jira Core
  • Jira Service Desk

Secure encryption for all transmitted data

The data sent between your instances can be encrypted

  • HTTPS connections are always encrypted
  • Email and file-based data can be secured with PGP encryption

Support for deprecated Jira Server versions

Unlike other Jira synchronization solutions, Backbone currently supports Jira server versions all the way back to 6.3 – which was released in mid-2014. The Jiras don't need to use the same Jira version, Backbone will handle the differences.

Synchronization from behind a firewall

Projects can exchange issue data via email or file exchange if you select the distributed configuration option. This lets projects synchronize even if they cannot reach each other directly. Read more about this use case.

Synchronization without installing Backbone

You can even synchronize with other Jira instances without installing Backbone there. Read more about this use case.