- 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
- 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 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
- Field mapping reference
- REST API
- Synchronization behavior
- Data Encryption
This year, Atlassian has announced to deprecate certain REST API endpoints as well as HTTP Basic Authentication with username and password for Jira Cloud starting on 1st of December 2018. That means, if you are synchronizing a Jira Server and Jira Cloud instance, please follow the steps in this article to make sure you're up to date.
Update Backbone Issue Sync on Jira Server
Please update your Backbone Issue Sync installation on your Jira Server to version 3.8.2 or higher.
Check if you already use an API token
- Go to https://id.atlassian.com/manage/api-tokens and login with the Atlassian account of your synchronization user.
- You can then view the list of API tokens you already use for this account.
- If you don't see any tokens, you are not using it yet.
- If you have some tokens, you have to judge yourself if you're using them already for your Backbone synchronizations.
- If you're not using it already, please create an API token, give it a meaningful name and copy the token to a temporary place.
Update synchronization to use an API token
Please go to the connection screen of the synchronization. In the upper right corner, you can edit the connection. Then you can enter the password for your Jira Server connection and the new API token for your Jira Cloud connection.
If you're not already using an email address as a user name, you might want to switch to an email address as detailed in this guide.
Do you need help?
Please email us at email@example.com.