Backbone Work Sync
5.24 5.23 5.22 5.21 5.20 Cloud Data Center
5.24 5.23 5.22 5.21 5.20 Cloud Data Center

Backbone Work Sync 8.9.0

November 17, 2026

You can now connect Backbone Work Sync to Jira Data Center instances behind a firewall or proxy. This release also adds an option to skip replaying status transitions and includes several bug fixes.

This release also contains fixes for security vulnerabilities notified in Backbone Work Sync Security Advisory 2026-11-17 and is a recommended upgrade.

Custom HTTP headers for Data Center connections

Some Data Center instances sit behind a firewall or proxy that only lets through requests with specific headers. In Backbone's global settings, you can now enter a Data Center base URL and the header names and values it needs. Backbone adds these headers to every request it sends to that instance. All synchronizations that connect to that instance use the same headers. Read more about adding custom request headers.

Improvements

  • Stricter text format templates: Backbone uses Apache Velocity for custom text formats, such as comment enrichment. This release restricts advanced Velocity features to improve security. If a text format no longer works as expected, check its template, or contact us for help.

  • Skip replaying status transitions: You can now choose whether Backbone replays the original work item's status transitions when it creates a work item on the other side. With replay off, new work items stay in their initial status. Later status changes still sync as usual. You can find more information on changing the option in this article.

New synchronizations don't replay status transitions by default. Existing synchronizations keep replaying them as before, and you can turn replay off if you don't need it.

Bug fixes

  • You can now publish a synchronization draft when Time tracking is a required field. Before, a warning blocked publishing, even after you mapped Original Estimate and Remaining Estimate.

  • Fixed an issue where attachments didn't load in a comment made public on the Jira Service Management side with your configured phrase.

  • Resolved an issue where comments that @mentioned a user with a hidden email address didn't sync when the sync.useDisplayNameUserMentions advanced setting was on. The sync panel stayed in an error status, and nothing appeared in troubleshooting.

Questions?

If something isn't working as expected, create a ticket in our help center or email help@k15t.com.

All Updates and Fixes in This Release

You can find all updates and fixes of this release in our Jira.

Last updated: