A question to all Jira users: Is it just me, or do the quirky scientist from the Big Bang Theory, Sheldon Cooper, and Jira Software have a lot in common?
I was recently (re)watching an episode and it hit me, it's uncanny how Sheldon Cooper is basically Jira in human form. Master of organization—check. Keeping track of due dates and dependencies for each project—check.
Sheldon's a genius in his own world, but social interactions? It's not his strong suit. Jira's the same. Perfect when collaborating within a Jira project but struggles when collaborating across different Jira instances and projects.
You end up with either manual copy-pasting issues or Jira automation headaches; neither is ideal. Thankfully, Sheldon has his friends helping him navigate through his social interactions, and Jira has Backbone Issue Sync to help communicate and sync issues across projects or instances.
That works as long as both sides using Jira have installed Backbone Issue Sync. What if your customer or partner can’t or doesn’t want to install apps? This is where Backbone Issue Sync’s Remote License comes in, which allows you to sync issues across Jira instances without installing apps on both side.
Now Imagine Sheldon trying to collaborate on a groundbreaking scientific research project with a team that refuses to use his preferred methods or tools. Chaos, right? This is similar to trying to sync Jira issues with your partners or teams on different Jira instances who don't want to use Backbone Issue Sync - or perhaps any apps.
Getting everyone on the same page, especially when installing apps, can be challenging. Convincing your partner to use the same app you use takes a lot of time and is sometimes impossible.
Like it or not, that's usually how sync apps work—both Jira instances need to install the app to sync issues. But what if your partner is a big enterprise with a gazillion rules about what software they can use? Maybe your partner just doesn’t have the time and budget or doesn’t want to bother. It can turn into a nightmare!
Enter Backbone Issue Sync's remote license, the first single instance management solution in the Jira sync apps market. The remote license allows you to sync issues across Jira instances without installing Backbone Issue Sync on your sync partner's instance. Bet Sheldon would've traded all his comic books if he was offered a way to never depend on others for anything in life.
The single instance management option is helpful in many situations, such as:
When your partner has a limited budget and can't afford other apps.
If your partner has strict IT policies and regulations and installing an app is not an option.
When dealing with large organizations that prefer not to install new software and change their workflows for a smaller partner.
In all of these scenarios, Backbone Issue Sync provides a simple solution—install a remote license on one of the Jira instances and start syncing without any blockers or delays.
You Have All The Control: No need to convince your partner to install and pay for the app. Installing Backbone Issue Sync only on your instance is sufficient, reducing the setup hassle.
Security Protocols? No Problem! Sync Jira data even if your partner can't install apps due to strict security settings. Of course, all data continues to be synced through highly secure, encrypted channels.
Quick Start, Big Results: Get up and running with a simple XML file and sync with full functionality of Backbone Issue Sync.
Less Fuss, More Sync: Change sync partner and connect to any number of Jira instances easily using the same license and without installing Backbone each time. Useful when you’re collaborating on short-term or temporary projects.
To start syncing with Jira instances where Backbone isn't installed, you just need to:
Install Backbone Issue Sync on your own Jira Cloud or DC from the Atlassian Marketplace.
Get a Backbone remote license by contacting us.
Upload the license file in Backbone Issue Sync’s configuration panel, and you’re off and running.
It is as simple as that. Once you've got your remote license, you can connect with any Jira instances you want with full functionality - as long as you have a corresponding sync user on the partner Jira.
The remote license option for Backbone Issue Sync has been available for Jira DC users for many years, but on popular demand, we're now extending it to Jira Cloud users as well. Read more about it in our release notes here.
Plus, we're introducing a user tier-based pricing model, making the remote license more affordable and suitable for all kinds of teams and budgets. Read more about the remote license model and pricing here.
Backbone Issue Sync's remote license gives you the independence to sync with other Jira instances without relying on your partners. Request a free 30-day trail or book a demo to discuss your needs.
Umer Sohail _K15t_
Product Marketing Manager
K15t
Germany
1 accepted answer
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
0 comments