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
Incoming Issue Error
Matthias Gaiser Last update: Mar 13, 2019
Symptoms
An issue does not get synchronized and appears in the troubleshooting section with the category 'Unknown' or 'Incoming Issue Error'.
Cause
An error happened while Backbone tried to synchronize changes to this issue.
Resolution
Incoming issue errors can happen for many reasons. Unfortunately, if you get linked to this page, this incoming issue error is being caused by a problem we haven't encountered yet, and we need to investigate further.
Please get in contact with our support team:
- Create a support ZIP as described in Analyse & Fix Errors
- Contact our support and attach the support ZIP in the ticket
2x$versions.current.name