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
- 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
- Field mapping reference
- REST 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
Migrate Jira projects
This use case describes how you can migrate Jira issues from a project on one Jira to another. This can be helpful when:
- Your company has recently acquired another company which also uses Jira and you want to merge both Jiras into one.
- Different departments of your company use their own Jira instance and you want to consolidate them into one.
With Backbone, you can migrate issue data between projects on Jira instances. To help with the transition, you can give the team access to both Jira projects for a time - Backbone keeps the issues in sync.
To maintain separate Jira instances, but continuously synchronize information between certain projects, check out bidirectional synchronization.
With Backbone, you can synchronize all issue data in a project from one Jira instance to another. To do this, you can configure a unidirectional synchronization from the Jira project on your source Jira instance to the one on the target.
- Since Backbone does not synchronize the project configuration data, manually create your target project or use another app to migrate the project configuration.
- After creating the target project, create a new synchronization.
- Then you can configure all the details. We recommend you to synchronize all information unidirectionally.
Congratulations! The basic configuration is now complete.
Good to know
- Usually, you need a Backbone license and installation on any Jira you want to sync with. However, with a remote license, you can also install Backbone only on your main (target) Jira instance and migrate as many Jira projects at a time as your remote license allows.
- The project configuration must be migrated either manually or automatically using another app.
- The issue key in the target Jira project may not be the same as the key in the source Jira project. This is because Backbone can't recognize if issues in the source Jira project were deleted or an error occurred when importing issues into the target Jira project. However, you can store the issue key from the source Jira project in a custom field in the target Jira project so you can preserve the information, see also our docs for the correlationFieldId.
- The history in the target instance will not look exactly the same as in the source. Read more how the issue history is handled.
- If you have many issues to migrate, we recommend to not synchronize all in one go, but rather in chunks. You can use the "Limit issues" functionality for that.
- If you want to do a soft migration, so that people can work in both projects for a while, you could use bidirectional synchronization instead of unidirectional or combine them.