Manual
-
Basics
-
Example Use Cases
-
Configuration
-
How-tos
-
Troubleshooting
- Analyze and fix errors
- Trigger a resync
-
Fix common problems
- General problem situations
-
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
- Error message reference
-
Administration
-
Reference
-
Backbone Issue Sync 3.8.2
-
Backbone Issue Sync 3.8.1
-
Backbone Issue Sync 3.8.3
-
Backbone Issue Sync 3.8.4
-
Backbone Issue Sync 3.9.0
-
Backbone Issue Sync 3.9.1
-
How can I only synchronize some comments
Scriptrunner: scripted fields
Sebastian Hesse Last update: Jan 30, 2019
Backbone Issue Sync provides support for the Groovy scripted fields of the plugin Scriptrunner. Scriptrunner offers the possibility to provide a script for such a field which calculates its value. These calculations can be based on other fields as well as data/logic outside of JIRA.
Since these fields cannot be updated manually by the user, Backbone does not allow incoming field mappings for fields of this type.
Info
The scripted fields never appear in the change history of a JIRA issue. Since Backbone is based on this change history, a change in a scripted field will only be synchronized when another field under synchronization is being changed in the source issue.