Backbone Work Sync 5.23.0

June 2026

We're happy to announce the release of Backbone 5.23.0, adding support for synchronizing the Team field and strengthening security by enforcing the Jira Allowlist for remote connections. We've also fixed an issue where project admins couldn't see sync status or troubleshooting errors and made migration scripts more resilient when encountering inaccessible work items.

Security Improvement: Jira Allowlist Enforcement

Backbone now validates all remote Jira connection URLs against your Jira Allowlist. This means for every sync to another instance, the URL must be explicitly listed in your Allowlist (found under Administration → System → Allowlist).

➡️ What you may need to do: if a connection stops working after upgrading, add the remote instance URL (e.g. https://your-instance.atlassian.net) to your Allowlist. No other configuration changes are needed. More information can be found in this article.

Team Field Synchronization

You can now synchronize the Team field between Jira spaces and instances. You can configure it like any other field mapping in your Backbone sync under field mappings, including a passthrough and correlation mapping.

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.

All updates and fixes in this release

Last updated: June 10, 2026