Manual
-
Basics
-
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
- Synchronize with Jira Service Desk
-
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
Synchronizations overview
Matthias Gaiser Last update: Mar 13, 2019
The main entry point of the Backbone UI is the synchronization overview which shows you a list of all existing synchronizations. You can find it either on a project level or a global level. Both screens offer the same set of actions you can do with your synchronizations.
Project synchronizations overview
Select Project settings > Issue Synchronization > ••• to manage your synchronizations for a single project:
Jira instance synchronizations overview
If you have Jira admin permissions, select Jira administration > Add-ons > Backbone Issue Sync > Synchronizations > ••• to manage all your synchronizations for the whole Jira instance:
Actions
Backbone has a range of functionality for managing synchronizations:
- Start/stop: enable or disable Backbone from syncing issues and issue data
- Edit: allows you to edit the name and description of a synchronization
- Configure: allows you to define what issue data gets synchronized between instances
- Troubleshoot: allows you to Analyze & Fix Errors
- Delete: allows you to permanently delete your synchronization. If the synchronization is not stopped, it will automatically be stopped.
If you're here for the first time, you should start with creating a new synchronization.