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
Start and stop synchronizations
Thomas Walker Last update: Oct 23, 2018
The state of a synchronization is displayed by a coloured text lozenge at the end of the each entry in the synchronization overview page (see Create and Update an synchronization for more details). If the synchronization is stopped it can be started from the Actions menu. As soon as the synchronization has been started the state will change to running.
Info
Please note that only a synchronization with a valid configuration can be started. If the synchronization is in an erroneous state a warning icon will be displayed at the beginning of the entry. Clicking this warning icon will lead you to the Troubleshooting screen which will give you further details on the error.
Additional actions
As you can see in the menu, Backbone offers some more actions on a synchronization.
- 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 Analyse & Fix Errors.
- Delete. Allows you to permanently delete your synchronization. If the synchronization is not stopped, it will automatically be stopped.
