Backbone Issue Sync for Jira by K15t

When a leading German industrial company started collaborating with a world-renowned automaker, both sides were using Jira to track issues and often needed to collaborate on the same issue – but neither partner’s users could log into the other‘s instance. This meant manually creating and updating equivalent issues in each instance which proved to be both inefficient and time-consuming.

Using Backbone Issue Sync, the partners can automatically synchronize issues between their instances, meaning that when an issue is created or changed in one instance, Backbone automatically applies the same update in the partner instance. Users can now work on equivalent issues without needing to copy-paste issue data between Jira systems – reducing overhead and keeping all stakeholders on the same page. Even connecting Jira instances from behind enterprise firewalls is no problem, thanks to Backbone’s ability to transmit is sue data via file exchanges.

Over time, one of the organizations introduced a new privacy requirement to hide certain field names and workflow states from their partner, while still keeping everything in sync. Backbone’s robust privacy settings now allows them to set aliases, rather than offer the actual field and status names, giving them total control over which configuration data is shared with or hidden from the partner. Furthermore, thanks to Backbone‘s ability to synchronize with remote instances without installing the app, the organization can also successfully synchronize with any partner, even those with especially tight security demands.

From the moment they synchronized their first issue, these companies have been successfully relying on Backbone to keep their teams in sync. Even within remote Jira instances – and despite occasional challenging conditions – they have been able to streamline their collaboration processes, letting them work better together.