Backbone Work Sync

Backbone Work Sync 8.3.0

September 2026


Syncing needs two spaces. Sometimes both exist, connect them using Backbone and you're done. When one doesn’t exist, someone has to build it first: work types, workflows, and screens recreated by hand or carried over via CSV. One space costs you an afternoon. Do it for every new client, partner, or team, and setup becomes the ceiling on how fast you can scale.

Introducing Quick Connect

Quick Connect creates that second Jira space for you, either in the same or across instances, cloned from a space you already trust and connected in the familiar sync setup flow.

For teams running dozens or hundreds of connected spaces, that changes what growth costs. Every new space starts from a proven configuration instead of a fresh round of manual setup, so onboarding a partner or customer takes minutes instead of hours. And the Jira space that comes out is already approved and ready to go. No missed work type, no workflow rebuilt slightly differently, no misconfigurations as you can have template spaces ready on your instance and clone and sync across all your partners.

Setting Up Quick Connect

In the New Synchronization wizard, you can now choose "Create and sync a new space" instead of selecting an existing one, both for your instance and your partner. Backbone clones the space you pick, optionally including its work items, and your sync partner gets an overview of what's getting cloned before accepting it.

What the clone carries: work types and their scheme, workflows and statuses, screens and screen schemes. Permission, notification, fields, field configuration, and security schemes start from your Jira defaults. More information is included in this article.

Note: A clone on its own is a disconnected copy of the Jira space, syncing it is a separate, deliberate step as before. Quick Connect puts both steps in one guided flow.

Improvements & Bug Fixes

Besides Quick Connect, this release includes several smaller improvements and fixes: duplicated comments, attachments, and worklogs when pairing work items; setting the correct default for the parent field; and unlinking more than 100 work items.

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

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


Last updated: