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
- Synchronize only certain issues
- Configuring the synchronization user
- Synchronizations overview
- Create a synchronization
- Synchronization detail view
- Issue Type Mappings
- Field Mappings
- Fields (Default values)
- Workflow Mappings
- Advanced Settings
- 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
- Custom Field Mapping Error
- 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
- Field mapping reference
- REST API
- Use the Java API
- Synchronization behavior
- Data Encryption
- Handling Personal Data
- How does Backbone affect server performance?
- Do you plan to synchronize with other systems?
- Does Backbone communicate via an encrypted channel?
- Can I synchronize an instance from behind an enterprise firewall?
- Can I synchronize an instance without installing Backbone?
- Can I have the same issue keys in both projects?
- Add a 'sync issue' button to the view issue screen
- Configure only changes made by one synchronization partner to be synchronized
- Rename the project key
- Stop synchronizations when Backbone is restarted
- Limit the synchronized issues
- Basic Authentication Change Notice
- Username Deprecation Notice
- Synchronization Message Flow
- Clear the sync info panel
- Change integration user to atlassian account
Synchronize only certain issues
This use case describes some examples of synchronizing only certain issues by filtering issues with a JQL statement. This can be helpful when you only want to sync a subset of issues from a certain issue type.
Only sync issues in a certain status
You might only want to sync an issue when it's in a certain status.
Example: you have the following statuses for an issue: Open, In Progress, Under Review and Closed. You only want issues that are In Progress and Under Review to be synced to the other project.
JQL statement: Status in ("In Progress", "Under Review")
Only sync issues with a certain value for a custom field
You might have set up some custom fields and based on the value of this field you want to synchronize it to the other project or not.
Example: you have the custom field "ComputerProblem" with the values "Hardware" and "Software". You only want issues with the value "Hardware" to be synced to the other project.
JQL statement: ComputerProblem = "Hardware"
Only sync issues based on date
You might only want to synchronize issues that are created after, before or on certain dates.
Example: you don't want all your old issues to be synced, only issues that are created after setting up the synchronization on the 9th of July 2019 should be synced to the other project.
JQL statement: createdDate >= 2019-07-09
Only sync issues with a certain label
You might have a label specified and only issues with that label should be synchronized.
Example: You want your users to specify for each issue if it should be synced to the other project by giving it the label "BackboneSync"
JQL statement: labels = "BackboneSync"
This guide explains how you can limit which issues are synchronized between two projects.
- Create a new synchronization between two projects.
- Configure Issue Type Mappings and Field Mappings.
- Go to Configuration > Issue Types > Limit issues and add your JQL statement for limiting issues to the project it should be applied to.
Good to know
- You can build your own JQL statement to make your custom selection of issues to be synced. The cases above are only some common examples.
- Note that it's also possible to combine multiple conditions.
- We offer the options to verify and run the JQL statements in the 'Limit Issues' dialog. These are useful options to check for errors and if you get the issues you expected.
- More tips for writing JQL statements can be found here.