Manual
-
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
- Component(s) not valid
- Custom Field Mapping Error
- 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 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
-
Administration
-
Reference
Restrict Backbone usage to certain projects
Thomas Walker Last update: Jun 4, 2018
Before you begin
You have to have access to the file system of your JIRA server to follow the steps laid out in this article.
If you want to allow only some projects to be synchronized with Backbone Issue Sync, you can do so by defining the following system properties:
- enableBackboneForAllProjects
By default this property is set to true, which lets all projects use Backbone. If you want to disable it for all projects, you should set this property to false. - backboneProjects
If "enableBackboneForAllProjects" is set to false, you can still enable certain projects to be synchronized with Backbone by listing them in this property. The value is a comma-separated list of project keys.
Info
If a project is disabled in this way, you cannot configure an synchronization from this project's administration screen. However, project administrators of enabled projects can integrate with all JIRA projects they have rights for, including disabled projects.
Example usage
-DbackboneProjects="AN,AA" -DenableBackboneForAllProjects="false"In this example, issue synchronization is disabled for all projects except those with project keys AN and AA.
Info
We are working on implementing this feature in a global administration UI. Please see BAC-519 for more details on progress.