Backbone Work Sync 7.2.0

May 2026

We’re happy to announce the release of Backbone 7.2.0, introducing a new onboarding experience that lets you instantly try Backbone by automatically cloning spaces and setting up a ready-to-use synchronization. And we’re inviting testers to preview the upcoming Quick Connect feature.

Get Started Page for Faster Onboarding

We’ve introduced a new on boarding flow to help new users quickly learn how to work with Backbone. This makes it easier to explore the core features of Backbone, without all the manual effort of setting it up

Try Out Backbone

A key feature is a simplified way to test Backbone and set up a sync:

  • You only need to select one space

  • We automatically clone it into two additional spaces, including up to 50 work items

  • A pre-filled synchronization is set up for you

This means you can immediately start experimenting with the sync behavior, without manually creating test spaces of syncs.

Why This Matters (Even for Existing Users)

Already familiar with Backbone? This is still useful:

  • Onboard new teammates faster
    Let new admins and other colleagues explore Backbone in a safe, ready-to-use setup

  • Test new use cases quickly
    Spin up experiments for new projects or client spaces without extra preperation

  • Validate setups before going live
    Try things out in a controlled environment using your own content

Coming Soon: Quick Connect

The cloning technology behind this experience is something we’re planning to bring directly into the app, specifically when you create a new synchronization.

We’re currently running a testing phase for this upcoming functionality.

👉 Interested in early access?
Reach out to us via help@k15t.com to join the testing group.

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

T Key Summary Status Resolution

Data cannot be retrieved due to an unexpected error.

View these issues in Jira