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 without installing
This use case describes how you can synchronize Jira issues with another Jira without installing anything there. This can be helpful when you want to:
- Synchronize one of your projects with a customer's project, but they don't allow to install an app in their Jira.
- Synchronize Jira issues between multiple Jira instances, but don't want to install and maintain Backbone in all Jiras.
- Synchronize Jira issues with a company, but you don't want to install an app for this.
To synchronize issues between Jira instances, you typically have to install Backbone in both Jiras and get a license from the Atlassian Marketplace for both.
However, Backbone offers a remote license model which you can use to install Backbone in only one Jira. The remote license is installed in the Jira where Backbone is installed (in addition to the marketplace license) and serves as a replacement for the license on the other Jira. Backbone will then use the Jira REST API in order to connect with the remote Jira.
This guide explains how you can synchronize your Jira with another without installing Backbone on the other Jira.
- Install Backbone from the Atlassian Marketplace in your Jira and get a usual (trial) license.
- Contact K15t to get a (trial) remote license and tell us how many Jiras you want to synchronize at the same time. We'll then send you a trial remote license.
- Install the remote license in your Jira.
- Create a synchronization with your partner and configure the synchronization details.
Good to know
- You can have multiple synchronizations as long as they synchronize issues with the same Jira instance to which the remote license applies.
- If you no longer have any running synchronizations with one external Jira, you can repurpose the remote license to synchronize with another.
- The Jira instance where Backbone is configured must be a Jira Server or Data Center.
- The Jira instance without the Backbone installation will not show a Sync Info Panel.
- The Jira instance with the Backbone installation needs to have HTTP(S) access to the REST API of the other Jira.