The glossary defines the core concepts and terminology of Backbone Issue Sync.
In the centralized configuration model, the synchronized Jira instances connect using the HTTPS protocol.
The synchronization is administered and run from a single Jira instance. Backbone must still be installed on the other JIRA instance, but this is only for licensing purposes.
note: this term is outdated, and not used in Backbone version 4.2 or higher.
|A field within a Jira issue. A field can either be a Jira system field or a custom field.
|A field mapping is the configuration which JIRA field of your project is being synchronized with a JIRA field of the partner project. Additionally, it contains further options like the direction of the mapping and how it should be mapped. For more details please refer to Field Mappings.
|The project where the synchronization was first created.
|The data that is synchronised belongs to an issue. Every issue has an issue type.
|The project you want to synchronize your project with.
|A type of Backbone license that lets you synchronize with JIRA instances where Backbone is not installed.
Sends the issue's current content to the synchronization partner.
|The project where the synchronization wasn't created, but which is still involved in the synchronization.
|The person running the Jira project that you are synchronizing with.
|A special user which has been created by installing Backbone into your environment. All changes that are synchronized from the partner project to your local one will appear as changes by the synchronization user.
|Sync info panel
|Small panel appearing in synchronized issues, that displays a variety of information on the issue's Backbone synchronizations.
|The troubleshooting tool identifies problems with synchronizations, and suggests steps to solve them.
|The mapping of which workflow states in the first project correspond to which workflow states in the second project.