Backbone Issue Sync 5.12.0
August 2024
This release contains a fix for a security vulnerability that can also be found in the Backbone Security Advisory. It is recommended to update to this version.
This release also includes the enablement of setting a default value for a group picker field and a bug fix.
Important update: if you are syncing your issue types unidirectional but update synchronized issues from both sides (e.g. statuses, comments), please switch the sync.syncUnsyncedIssueTypeAllowed in the advanced settings on both sides to “yes“ to allow these updates to come through. This was needed due to a fix for a security vulnerability on Jira Cloud. We assumed this was also applicable to Data Center, hence we’ve also implemented it here. If you are on Data Center, switching it to “yes“ shouldn’t cause any data leakage.
Please note that if you don’t make this change, the updates will also only be synced unidirectional (similar to the issue type mapping).
Group Picker Field in Default Values
A default value in your synchronization allows you to automatically pre-populate fields with predefined data when Backbone creates an issue. We've expanded the capabilities of default values by introducing a new field type you can set: Group Picker. More information on default values can be found in this article.
New Advanced Feature: Control over Non-Included Issue Types
In the advanced settings of the configuration you can now find the option: sync.unsyncedIssueTypeAllowed. This option gives you control over whether it’s allowed to synchronize issue data, even for issue types that are not explicitly included in your synchronization settings. By default this is turned off, and thus not allowed. We have introduced this option due to the security vulnerability found on Jira Cloud (see the Backbone Security Advisory).
Questions?
Do you have questions, or is something not working as expected? Please let us know by creating a ticket in our support system or emailing help@k15t.com.