Manual
-
Basics
-
Runtime
-
Example Use Cases
- Bidirectional synchronization
- Unidirectional synchronization
- Synchronize Jira Server with Jira Cloud
- Synchronize one project with multiple others
- Synchronize a private with a public project
- Synchronize projects behind firewalls
- Synchronize without installing
- Synchronize with changing Jiras
- Migrate Jira projects
- JIRA Service Desk
-
Centralized configuration
-
Distributed configuration
-
How-tos
-
Troubleshooting
- Analyze and fix errors
- Trigger a resync
- Increase the JIRA logging level
-
Fix common problems
-
General problem situations
- 411 - Length required
- All fields have English names although Jira is in a different language
- Authentication with an external Jira fails
- Exception: ServiceLocatorImpl has been shut down
- Sync info panel displays wrong synchronization name, and no link to partner project
- Server is not reachable - how to fix it
- Changes are not being synchronized
- Can't change the synchronization user
- Recently created issue types, fields, etc. are not available when editing configuration
-
Issue specific problem situations
- Admin or project admin permissions are required
- Bad gateway
- Cannot add or remove watcher
- Cannot create new issue without mapped issue type
- Cannot find transition
- Cannot find transition id
- Component(s) not valid
- Field not on the Screen
- Incoming Issue Error
- Incompatible message format
- Invalid license
- Invalid regex syntax
- Issue does not exist
- Issues must be assigned
- JIRA is offline
- Missing attachment permissions
- Missing Issue
- Missing issue type mapping
- Missing message
- Missing parent Issue error
- Missing required fields
- No create version permissions
- No permissions to view this request for JIRA Service Desk
- No project administration permissions
- Option not valid
- Outgoing Issue error
- Outgoing Send Error
- Priority not valid
- Resolution cannot be chosen
- Sprint does not exist
- Template error
- The requested board cannot be viewed
- User does not exist
- User not assignable
- Version(s) not valid
- Workflow operation not valid
-
General problem situations
-
Administration
-
Reference
Key features
Matthias Gaiser Last update: Mar 12, 2019
Backbone has multiple features that make synchronizing issues flexible and powerful.
Support for all Jira deployments and applications
Backbone lets you synchronize issues between all kind of JIRA deployments:
- Jira Server ↔ Jira Server
- Jira Server ↔ Jira Cloud
- Jira Cloud ↔ Jira Cloud
And all kinds of Jira applications:
- Jira Software
- Jira Core
- Jira Service Desk
- Jira Data Center
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.
Control what's synchronized, and in what direction
Backbone supports unidirectional and bidirectional synchronization of all issue types, and selective synchronization of issues and fields based on JQL conditionsns.
The following issue data can be synchronized:
And more...
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.
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
Synchronization without installing Backbone
If you use a remote license (only available on Jira Server instances), you can synchronize with other Jira instances without even installing Backbone there.