$home.properties.pagetreeHeading.asText
-
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 without installing
- Migrate Jira projects
- Synchronize with Jira Service Desk
- Synchronize only certain issues
-
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
- 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
- Could not resolve value of Issue Key
-
Administration
-
Reference
-
Backbone Issue Sync 3.9.3
Priority not valid

Matthias Gaiser Last update: Mar 13, 2019
Symptoms
An issue does not get synchronized and appears in the troubleshooting section with the category 'Priority not valid' and the message, e.g. '"priority":"Priority name 'Major' is not valid"'.
The 'priority' part identifies the internal id of the field which is affected.
Cause
A priority was set to the issue in the sender project and is mapped to a value which is not a valid priority in the receiver project. This can be due to an invalid mapping configuration in Backbone or a missing configuration in the receiving project.
Resolution
The following steps should be done in order to resolve this problem.
- Check the priority configuration of the receiving project if all priorities are configured the desired way.
- Access the Field Mappings configuration, edit the corresponding priority field mapping and check that your priorities are mapped correctly. If you use the Passthrough Mapping and your priority names are different in the two projects, please use the Priority Mapping and map the desired priorities to each other.
- After fixing your configuration...
2x$versions.current.name