- Basics
-
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
- Configuration
- How-tos
-
Troubleshooting
- 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
- Administration
- Reference
-
FAQs
- 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?
-
Knowledge Base
- 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 one project with multiple others
This use case describes how you can synchronize one Jira project with multiple other projects. This can be helpful when you:
- Manage all tasks in one Jira project, while not all tasks are done by your team, but also by teams or companies which don't work in your Jira project.
- Work for multiple teams or companies but want to collect all tasks in one Jira project.
To do this, set up multiple synchronizations, one for each project you want to connect to the single project. Backbone takes care of the automated issue synchronization. You can choose if you want to share certain tasks with multiple partners, or only each task with a specific partner.
Configuration guide
In this guide, we will configure a Jira project (project A) so it synchronizes issues with multiple other projects (project B and C).
- Create a new synchronization between project A and B
- Configure issue type and field mappings according to your needs.
- Setup a JQL query to limit the issues you want to sync with project B. We recommend you to use Jira's advanced search to find criteria which suits your needs, e.g. "component = projectB".
- Create another synchronization between project A and C. We recommend you to use a different synchronization user (see also "Good to know" section).
- Configure issue type mappings and field mappings according to your needs.
- Setup a JQL query to limit the issues you want to sync with project C. We recommend you to use Jira's advanced search to find criteria which suits your needs, e.g. "component = projectC".
Congratulations! The basic configuration is now complete. You can now add attachment, comment or workflow mappings if desired.
Good to know
- If you want to synchronize the changes not only from project B to A, but also from B to C via A, you will need a different synchronization user for the connection details of project A. We recommend you to use different synchronization users so you can decide later if you want that behavior. Please note that in Cloud to Cloud scenarios, you cannot use different synchronization users at the moment.
- If you want to synchronize each task with one partner only, make sure your JQL queries are well-defined and tasks don't accidentally qualify for multiple synchronizations. A single select field can be a perfect criterion.