Depending on your needs, Backbone Issue Sync has two separate licensing models:
- Atlassian Marketplace licensing – the standard licensing model, where Backbone must be installed on all synchronized Jira instances (recommended option).
- Remote licensing – this requires more manual setup, but Backbone only needs to be installed on one Jira Server instance, but still licensed for all instances.
This article explains when and how to license Backbone using either of these models.
Backbone Issue Sync needs to be licensed for each Jira instance you want to synchronize with. This is independent of which licensing model you choose.
Atlassian Marketplace licensing
When should I use it?
This is the standard licensing model. We recommend this option whenever it's possible to install Backbone on all synchronized Jira systems.
It's quicker to set up than the Remote licensing model, and renewals are automatic, saving time for you. In every Jira all Backbone features can be used and new synchronizations with other projects initiated.
What license size do I need?
The Backbone license size must always be the same as the license size of the base Jira instance it is installed on.
How does Jira service desk licensing work?
As stated before, you only need a license that corresponds to the user tier of the largest Jira application in your instance. For example, if your Jira software instance were 200 users, and your JSD license were 10 users, you'd need a 200 user license for the instance.
Where can I get it?
You can purchase an Atlassian Marketplace license directly from the Atlassian Marketplace, or from your Atlassian partner.
When should I use it?
When you can only install Backbone in one Jira instance.
A remote license can replace a usual Atlassian marketplace license for another Jira instance, so the other instance does not need to install or license Backbone. You still need a marketplace license for your local Jira instance and in addition the remote license.
You can only install a remote license on a Jira Server instance. A remote license only works with the Centralized Configuration model, but besides that the full issue synchronization feature set is available.
Where can I get it?
Remote licensing is not available on the Atlassian Marketplace – if you are interested in remote licensing, please contact us via the contact form of our remote licensing page.
How does it work?
Remote licensing lets you connect to other Jira instances using remote endpoints. When you buy a remote license, you can specify to have as many remote endpoints as you want (the more you buy, the more expensive the license).
From the instance where you install the remote license (let's call it instance A) you can create synchronizations with other partner instances, regardless of if they have Backbone installed and licensed. For every partner instance where Backbone is not installed and licensed, one of the endpoint licenses of instance A's license is consumed. If you try to use synchronize with more instances than you have endpoint licenses, you will get an error and wont be able to start the synchronization.
As soon as you stop all synchronizations using this Jira as an endpoint, the endpoint license will be released, and can be used in other synchronizations.
Example license file
In the license file, you can verify your expiration date and the amount of your remote endpoints:
<?xml version="1.0" encoding="UTF-8"?> <license> <info> <creation>2017-05-11</creation> <holder>IT Unicorns Inc.</holder> <creator>K15t Software GmbH</creator> <product>Backbone Issue Sync for Jira</product> </info> <policies> <policy type="PRODUCT_KEY">com.k15t.backbone.backbone-issue-sync</policy> <policy type="EXPIRATION">2017-07-10</policy> <policy type="MAX_REMOTE_ENDPOINTS">1</policy> </policies> <signature>qwertyuiopasdfghjklzxcvbnm</signature> </license>
How do I install the license?
To install a Backbone remote license, simply place your license file, backbone-issue-sync-license.xml, into the folder <JIRA_HOME>/data/backbone-issue-sync. You might have to create the backbone-issue-sync folder yourself. If you are using JIRA Data Center, place the license into the shared home directory in the corresponding path, and not in the local home directory.