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
Sync info panel
Matthias Gaiser Last update: Feb 26, 2019
Backbone adds a Sync Info Panel to the view issue screen of all issues in your JIRA system, and displays a variety of information on the issue's Backbone synchronizations:
| Synced with | The issue key of the partner issue |
|---|---|
| Sync Status | UP TO DATE All changes have successfully been synchronized PENDING You have made changes that have not yet been confirmed as successfully synchronized by the partner instance ERROR There is a problem with the synchronization, and it has stopped working properly. If you hover over the error message, a tooltip will appear that shows you if the error is in your instance or the partner instance |
Last received/sent | The time when the issue last received changes from the partner instance or sent changes to the partner instance |
Hide/display the panel
By default, the Issue Sync Panel is visible to all JIRA users – but JIRA or project administrators can define which users can see the panel, and who can't.
- Firstly, define which users should be able to see the panel using the View Backbone Issue Sync Panel permission (this is configured like any other JIRA permission).
- Now you can restrict the Issue Sync Panel on a global level – or for individual projects – by navigating to Project settings > Issue Synchronization and clicking Restrict Issue Sync Panel for all projects or Restrict Issue Sync Panel for project <project key>:
Troubleshooting
When someone uses Backbone without assigning project admin permissions to the synchronization user, the synchronization name won't be displayed in the Issue Sync Panel, and the issue won't be linked. There are two ways of fixing this problem.