Manual
-
Basics
-
Runtime
-
Example Use Cases
-
Centralized configuration
-
Troubleshooting
- Analyze and fix errors
-
Error message reference
- Admin or project admin permissions are required
- 411 - Length required
- Bad gateway
- 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 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
- Server is not reachable - how to fix it
- 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
- Fix common problems
- Configure email error notifications
-
JIRA Service Desk
-
Reference
-
Administration
-
Backbone Issue Sync 3.8.2
-
Backbone Issue Sync 3.8.1
-
Backbone Issue Sync 3.8.3
-
Backbone Issue Sync 3.8.4
-
How can I only synchronize some comments
Component

Thomas Walker Last update: Jun 4, 2018
Backbone has multiple options for synchronizing the component field.
Same component to same component
If you want to synchronize all issues to the same component value in both instances, simply select the Components Passthrough Mapping option.
Info
If one synchronization partner tries to synchronize a component with an instance without a component with the same name, the synchronization won't work. To avoid this, select Create missing components to automatically create a component with the same name in the partner instance when the synchronization is initialized.
Specific component to specific component
You can synchronize specific components to other specific components (for example, you can synchronize issues in component '30' in Project A to component 'Thirty' in Project B).
To do so, select the Components Field Value Mapping setting, and in the Component mapping section, click Add Entry to enter the components you want to synchronize. The components are mapped according to the number they are assigned to – so the component assigned to number 1 on the left side will be synchronized to component 1 on the right side.
You must also select a default component for the issue to be mapped to in case you are synchronizing a component that you haven't created a mapping for. You can do this using the Default component dropdown.