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
Add a 'sync issue' button to the view issue screen
If you do not want issues in a project to be synchronized by default – but only after a user has manually authorized the synchronization – then you can add a 'sync issue' button to the issue screen, letting you authorize synchronization on an issue-by-issue basis.
The method behind this is simple. First, we'll configure Backbone to only synchronize issues with a certain label, then we'll create a workflow transition button which will assign the issue that label when clicked.
1. Set only issues with a certain label to be synced
First, we'll limit the synchronized issues, so that only issues with the label 'sync' are synchronized (you can use any requirement, this is just an example).
To do this, navigate to the 'issue types' tab on the synchronization configuration, then click 'limit issues'. For your scenario, this JQL should work:
Now, only issues with the label 'sync' will be synchronized to the partner instance.
2. Edit the project workflow
Now, we need to edit the project workflow, to add a workflow transition which will automatically assign the label 'sync' when triggered.
- Edit the workflow for the project (and, if needed, issue type) you want to add the button to, and add a global looped transition (from any status to itself)
- Assign a POST function to this transition which modifies the issue so that it qualifies for the sync. In our example, this POST needs to add a label named 'sync'. You need to use an add-on such as Scriptrunner to set labels with a POST function.
Now, your sync button will appear when you view issues and you can click it to trigger the issue to be synced.