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
- Cannot perform transition
- Component(s) not valid
- Could not resolve value of Project Key
- Fallback user does not exist
- Field not on the Screen
- Incoming Issue Error
- Incompatible message format
- Invalid JQL Filter
- 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 project administration permissions
- Option not valid
- Outgoing Issue error
- Outgoing Send Error
- Priority not valid
- Resolution cannot be chosen
- Security level name is not valid
- 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
Supported Jira versions
Sebastian Hesse Last update: Mar 29, 2019
This article explains what versions of Jira can be synchronized with one another using Backbone Issue Sync.
Server ↔ Server
Backbone Issue Sync supports Jira Server versions 6.3 and higher. All supported versions can be synchronized with each other – e.g. you can synchronize a Jira 6.3 instance with a Jira 7.x instance.
We suggest to read the related example use cases, e.g. how to setup a bidirectional synchronization.
Server ↔ Cloud or Cloud ↔ Server
All supported versions of Jira Server can be synchronized with Jira Cloud and vice versa. In this case, a synchronization needs to be configured on the Jira Server side. Please read this Example Use Case article which explains the initial setup steps and best practices. However, please note that distributed configurations are not supported.
Cloud ↔ Cloud
Also Jira Cloud instances can be synchronized with each other. This is documented in the cloud section of our documentation.