It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Use Case: Collaborating Across Jira Instances with Backbone Issue Sync

This article is extracted from The Hitchhiker’s Guide to the Atlassian App Galaxy, a free e-book that features real-world use cases for 25 of the coolest apps in the Atlassian ecosystem. Download your copy today to learn how businesses just like yours are using popular Marketplace apps to extend innovation and collaboration in their organizations.

The universe of Jira integrations is constantly expanding. As more companies discover the power of Jira for everything from DevOps to Sales and Marketing, there’s an ever-growing demand to connect Jira to the other systems that make their businesses run.

Out of all the integrations out there, one of the simplest and most powerful integrations is Jira to Jira. This allows business teams and partners to collaborate across internal and external Jira Cloud, Server, Data Center, Service Desk, and even firewall-protected instances – without losing a step.

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.

AutomatedJiraIssueSynchronization_BackboneIssueSync.png 

Using Backbone Issue Sync for Jira, from K15t Software, 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 issue data via file exchanges.

BackboneIssueSyncScreenshots.png 

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

This is just one of many use cases featured in The Hitchhiker’s Guide to the Atlassian App GalaxyDownload the full guide to see them all.

4 comments

Thank you @Matthew Lewsadder for sharing the article.

The Hitchhiker’s Guide to the Atlassian App Galaxy was also distributed as a hard copy at the Atlassian Summit in Barcelona this year. If you ask the Communardo team kindly, they might even have some left.

And if someone has questions about Backbone, feel free to reach out to our team via support@k15t.com. Or ask them here and we'll do our best to answer it.

Cheers,
Matthias.

Is it possible to trigger a sync between instances from the source based on all-projects (project-independent) condition? Example - I have multiple SDLC projects in JiraA which need to trigger an issue creation in a specific project in JiraB. Is that achievable with Backbone?

Hi @Dimitar Dimitrov,

it is possible to sync multiple projects in Jira A with one specific project in Jira B, however it is not possible to have one condition across multiple projects. You'd have to create multiple synchronizations between each project in Jira A and the one in Jira B.

We've decided for this model in order to avoid misconfigurations because multiple projects can use different project configuration in terms of versions, components, issue types, boards.

Cheers,
Matthias.

Acknowledged, thank you!

Comment

Log in or Sign up to comment
Community showcase
Published in Marketplace Apps & Integrations

Localize Smarter with the Transifex Integration for Bitbucket

Over 52% of internet users say obtaining information in their own language is more important than price and 75% of the world’s population doesn’t speak English. It’s no wonder then that successful gl...

251 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you