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.8.0

November 4, 2026

With this release, changes can now travel through several synced spaces instead of stopping after one. All it takes is a Jira service account. You can now also choose to sync only recent comments, worklogs, and attachments.

Pass changes through more than two spaces

Work often passes through more than one team. A customer request lands in your general service desk, moves to a dedicated support team, and ends up with engineering. Each team works in its own space, and you sync each space with the next.

Until now, changes only traveled one step. A comment from engineering reached the dedicated support team but stopped there. The service desk space, and your customer, never saw it.

Now changes can pass through every synced space, in both directions. Set up one of the two synchronizations with a service account. The engineering comment then reaches your service desk automatically. This works the same way it already does on Data Center.

Where this helps:

  • Support escalation: Your service desk syncs with support, and support syncs with engineering. Status updates and comments flow all the way back to your customer.

  • Internal review before sharing: Your team works in an internal space and passes work to a review space. Only the review space syncs with your customer's Jira.

  • Partner hand-off: Your internal space syncs with a coordination space, which syncs with a vendor's Jira.

Service accounts help in any synchronization:

  • Traceability: See which synchronization made a change. Give each synchronization its own service account with a clear name.

  • Control over access: Decide exactly what a synchronization can do. You set the service account's permissions and scopes yourself.

  • A name your team recognizes: Synced changes show the service account's name instead of the app user.

How to Set It Up?

You can find all information on how to set up a service account, what permissions it needs and how to use it in a synchronization in this article.

Improvements

Sync only recent comments, worklogs, and attachments: Set a cutoff date and time, and your space only sends comments, worklogs, and attachments added or changed after it. This keeps old history out of the other space. It also prevents duplicates when you move work items to a new synchronization. Fields aren’t affected and still sync their latest value. Each side has its own cutoff, which you set with the sync.commentsWorklogsAttachmentsSince advanced setting.

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: