$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
Missing Issue

Matthias Gaiser Last update: Mar 13, 2019
Symptoms
An issue does not get synchronized and appears in the troubleshooting section with the category 'Missing issue' and a message like 'The Issue PA-123 is preventing the Issue PA-234 to be processed.'.
Cause
There are two possible causes:
- A subtask is being synchronized, but its parent task is not synchronized.
- An issue is assigned to an epic and the epic is not synchronized.
Resolution
- Check why the required issue is not being synchronized
- It might not be in the set of synced issues - check your JQL filter and the Issue Type Mappings.
- It might appear in the troubleshooting with an error which prevents its creation.
As soon as the parent/epic issue is being synchronized, Backbone will try to apply the message again.
2x$versions.current.name