Say Hello to Backbone Work Sync (Good-Bye, Issues!)

Umer Sohail Product Marketing Manager

Published on April 10, 2025 in

2 minute read

metaDescription	As Jira's "issues" move to work and work items, Backbone Issue Sync is now Backbone Work Sync, reflecting Atlassian's update.
shareTitle	Say Hello to Backbone Work Sync (Good-Bye, Issues!)
shareDescription	Atlassian updates "issues" to "work," and Backbone Issue Sync becomes Backbone Work Sync for Jira.
shareImage
teaserImage
teaserText	As Jira's "issues" move to work and work items, Backbone Issue Sync is now Backbone Work Sync, reflecting Atlassian's update.
author	Umer Sohail
heading	Say Hello to Backbone Work Sync (Good-Bye, Issues!)

Buckle up; Jira’s about to get a makeover, and so is our app! Backbone Issue Sync for Jira is now Backbone Work Sync for Jira. This follows Atlassian's recent update as they move from "issues" to "work" to better represent the diverse ways teams use the platform. Here’s the latest announcement post by Atlassian.

Why the Change?

Atlassian and K15t are ditching the old "issues" label because your tasks are more than just issues (read problems). Jira and syncing projects using Backbone offer much more than just a solution to headaches. You're orchestrating project symphonies, building marketing magic, and squashing digital bugs.

So Atlassian and K15t are swapping issues out for something that fits everything: "work."

You were already syncing your tasks, stories, epics, and JSM tickets, which weren’t represented by the term “issues”. Now you decide what your "work" looks like, and Jira and Backbone Work Sync will be there to empower you.

What Does This Mean for Backbone Users?

The core functionality of Backbone remains unchanged. You can still seamlessly synchronize work items (bugs, tasks, stories) between Jira instances, regardless of their specific type. Here are some of the changes you can expect to see in the coming days:

Touchpoint Changes: You'll see "work" or "work item" replacing "issue" in our UI, documentation, and communication. You might notice some inconsistencies as we standardize the terminology across all assets.
Workflow Continuity: Your existing syncs and configurations will continue functioning as expected. You won't need to recreate or adjust your setups due to this terminology change.

Steps You Might Need to Take

You won't need to take any specific action. The update is primarily a terminology change.

However, we recommend:

Updating any internal documentation or training materials that refer to "Backbone Issue Sync" to reflect the new name.
Clarifying with your teams that for Jira, this change is currently rolling out only for Cloud users, and the term “issues” will remain if you're using Jira Data Center (DC). However, Backbone users will see the name change across all types of hosting.

Evolving to Meet Your Collaboration Needs

This change is part of how Backbone Work Sync continues to improve and prioritize providing users with a seamless experience while staying ahead of the curve with the latest advancements by Atlassian.

Let's bid farewell to "issues" and say a big, hearty hello to all the fantastic "work" you're doing.

Share this article ✕