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
Synchronize Jira Server with Jira Cloud
This use case describes how you can synchronize Jira issues between a Jira Server and a Jira Cloud instance. This can be helpful when you want to:
- Synchronize a private with a public project
- Synchronize issues with a partner who is using Jira Cloud while you are using Jira Server or vice versa.
Backbone supports the full set of features to synchronize issues between Jira Server and Jira Cloud. The only limitation is having to configure it on the Jira Server side.
In this guide, you will configure Backbone so that it synchronizes issues between a project on Jira Server and a project on Jira Cloud. This guide assumes the other project already exists.
- Install Backbone Issue Sync in both Jiras.
Create a new synchronization between both projects in the Jira Server instance.
- When creating the synchronization, you need to enter the url of the Jira Cloud instance (like https://example.atlassian.net) as well as user details for a synchronization user of the Jira Cloud instance.
- Use the email address and an API token for the synchronization user details of the Jira Cloud instance.
- Configure Issue Type Mappings and Field Mappings.
Good to know
- Synchronizations between Jira Server and Jira Cloud are always configured on the Jira Server side. A distributed configuration setup for a synchronization between Jira Server and Jira Cloud is not supported at the moment.
- Backbone must be installed and licensed on both sides. Not possible? Learn about remote licenses.
- The Jira Server instance must be able to connect to the Jira Cloud instance and our backend on https://backbone-issue-sync.addons.k15t.com via HTTPS. No connection from Jira Cloud to Jira Server is necessary.