Backbone Issue Sync 3.1.9-AC
September 2024
In our previous release, we introduced a new advanced setting (sync.unsyncedIssueTypeAllowed) to give you more control over which issues are synchronized, aiming to prevent data leakage when using the "review mode." However, this change also stopped bidirectional synchronization for fields, statuses, attachments, and comments when issue types were set to sync unidirectionally.
Based on your feedback and with a continued focus on security, we've updated this advanced setting to restore bidirectional syncing by default while ensuring robust security measures remain in place. This update will be applied automatically to your existing sync configurations.
With this release, we’ve also fixed the functionality of the advanced setting advanced.issueTypeChangeAllowed and a bug regarding the sync info panels that showed an error while none are reported in the troubleshooting.
Please read below for more detailed information on these changes and how they impact your usage.
Updated Advanced Setting
The advanced setting sync.unsyncedIssueTypeAllowed has been updated to offer three levels of control over issue type and field synchronization. You can choose between the following settings:
All:
Values (such as fields and comments) will sync bidirectionally, even if the issue type is only synced unidirectionally.
If an issue type is changed to one not included in the sync, updates will still continue for that issue type.
Potential risk (only for "review mode" syncs): Issues could be paired with types that aren't meant to be synced, which may lead to data leakage.
Any direction (Default):
Values (such as fields and comments) will sync bidirectionally, even if the issue type is only synced unidirectionally.
If an issue type is changed to one not in the mapping, syncing will stop for that issue type.
Configured Directions
Values (such as fields and comments) will not sync bidirectionally if the issue type is only synced unidirectionally. The direction of syncing for issue types also applies to field mappings, statuses, comments, and attachments.
You have the following configuration:
Sync between project A and project B
Issue types (unidirectional):
Bug → Bug
Field Mappings (bidirectional):
Description ↔︎ Description
You create a bug in project A (PA-1) which gets synced to project B (PB-1). The table below shows what does and doesn’t get synced based on the configuration.
Action | All | Any Direction | Configured Direction |
|---|---|---|---|
Update description in PA-1 | description synced | description synced | description synced |
Update description in PB-1 | description synced | description synced | description not synced |
Change issue type PA-1 from bug to a task and update the description on PA-1 | description synced | description not synced | description not synced |
What do you have to do?
In general, you don’t need to do anything. We will update the setting for you as follows:
If you haven’t modified the
sync.unsyncedIssueTypeAllowedsetting (previously set to “no”) or set it back to “no,“ it will be updated to "Any direction."If the
sync.unsyncedIssueTypeAllowedsetting was previously set to “yes,” it will be changed to the new "All" option.
For new synchronizations, the default setting will be "Any direction."
Questions?
Do you have questions, or is something not working as expected? Please let us know by creating a ticket in our help center or emailing help@k15t.com.