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
Configuring the synchronization user
Sebastian Hesse Last update: May 6, 2019
The synchronization user is a normal Jira user that Backbone uses to apply incoming issue updates. Every synchronized Jira instance requires its own synchronization user.
This article explains how to create and configure the synchronization user correctly.
1. Create the synchronization user
Since the synchronization user is a Jira user, you create it just like you create a normal Jira user. Please note:
- You shouldn't log in and make manual changes as this user – it should only be used by Backbone. This is because changes made by the synchronization user are never synchronized by Backbone
- Only one synchronization user is required per instance, because the synchronization user can be re-used for multiple synchronizations
- You need to create a synchronization user in every Jira instance you are synchronizing
2. Assign the required permissions
Just like a normal Jira user, the synchronization user requires certain permissions to perform certain actions – such as creating issues or transitioning workflow statuses.
Basic configuration
The simplest method is to add the synchronization user to the 'Project administrators' role in all projects you want to synchronize.
The synchronization user will then be able to perform all required actions.
Advanced configuration
In situations where you want more fine grained control, you can assign the sync user only the permissions it needs to perform the actions you require.
| Functionality | Required permissions |
|---|---|
| Synchronize issues |
|
| Synchronize workflow statuses |
|
| Synchronize comments |
|
| Synchronize attachments |
|
| Synchronize watchers |
|
| Synchronize issue links |
|
| Use sync info panel |
|
Info
If you are synchronizing a Jira Service Desk project, please assign the sync user to the 'Service Desk Team' role and make him a Service Desk Agent. Otherwise you won't be able to use all Jira Service Desk features within your synchronizations. Read more in the help articles about Jira Service Desk.