- 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
- 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 parent Issue error
- 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
- 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
Backbone Issue Sync allows you to integrate two Jira projects to synchronize issues.
Scope of a synchronization
Synchronizations are always configured on a project-by-project basis, always between two projects.
However, you can create multiple synchronizations per project. So if you want to connect one project with multiple projects, you can simply create multiple synchronizations for a project.
Data transmission protocol
Backbone uses the official Jira REST API in order to access both Jira projects which it integrates. If you provide a HTTPS URL when you setup the synchronization, Backbone will use an encrypted channel in order to communicate with JIRA.
Create a synchronization
- Firstly, open the project where you want to configure the synchronization then select Project settings > Issue Synchronization > New Synchronization > Centralized Configuration.
- Now, you can start configuring the synchronization:
In Base URL, enter the Base URL of your JIRA instance.
- If you want to configure the synchronization with a proxy forward proxy server (e.g. to exit a DMZ), check Use Proxy, and click Enter Custom Proxy to add your login credentials for a proxy server that your JIRA can forward its requests to. For the proxy server address, you have to specify the full URL, including 'http://' or 'https://'.
- In Synchronization User enter the synchronization user's username (in this example, that's syncuser).
In Sync user password, enter the synchronization user's password.
- On the next screen, you can select which project you want to synchronize with:
- Next, you can assign the synchronization a name and description. When you make multiple synchronizations for a project, it's important to name them descriptively, so you don't get them confused. However, for now, let's stick with the default.
Congratulations, you've established a synchronization! Now, carry on and configure what issue types will be synchronized between the projects.