Licensing and paid via Atlassian listings
How can I make my add-on use Atlassian licenses?
To list a paid via Atlassian plugin, you must use Atlassian's licensing system. You can do so by using the Atlassian Licensing Support API in your plugin. You can find a tutorial here Tutorial: Adding licensing support to your add-on (up to UPM version 2.0).
What is a license end date?
Just like Atlassian products, customers can get an evaluation license or purchase a standard Atlassian license for a paid via Atlassian listing. Customers receive an evaluation license when they choose the Free 30 day Trial button on the Marketplace or the Try button in the Universal Plugin Manager (UPM). An evaluation license allows a customer to use an add-on until the evaluation period end-date is reached. After the 30-day evaluation period, the add-on's license enforcement mechanism engages and the add-on becomes invalid. (As the add-on vendor, you determine how the add-on functions in response to an invalid evaluation license).
Standard Atlassian licenses allow users to perpetually use an add-on. Customers receive a standard license when they choose the Buy License Now from the Marketplace or the Buy button in the UPM. A standard license gives your customer maintenance for a year from date of purchase. Maintenance includes support and access to any version upgrades for a year from date of purchase. One year after purchase, the maintenance expires and the customer must renew the license to receive support or maintenance for the next 12 month period.
How does a license determine a maintenance start and end date?
Maintenance is valid for one year after purchase. The maintenance-start and -end date are encoded into the license. The Atlassian Licensing system reports whether licenses are in maintenance. To determine license maintenance for a given version of your add-on, the maintenance-start and -end date of the license is compared against the build-date of your add-on.
Find out more about maintenance here: http://www.atlassian.com/licensing/purchase-licensing#softwaremaintenance-3
How do evaluation or trial licenses work?
Just like Atlassian products, customers can get an evaluation license or purchase a standard Atlassian license for a paid via Atlassian listing. Customers receive an evaluation license when they choose the Free 30 day Trial button on the Marketplace or the Try button in the Universal Plugin Manager (UPM). An evaluation license allows a customer to use an add-on until the evaluation period end-date is reached. After the 30-day evaluation period, the add-on's license enforcement mechanism engages and the add-on becomes invalid. As the add-on vendor, you determine how the add-on functions in response to an invalid evaluation license.
In certain cases, an add-on evaluation can be longer than 30 days, particularly in Atlassian Cloud. The add-on evaluation will actually end on the next billing cycle date after a full 30 day evaluation period. Read more here: Sales and evaluations reports for paid via Atlassian listings
How do Academic licenses work?
To support education and encourage the next generation of software developers, Atlassian offers all of our software at a 50% discount to qualified academic institutions. Paid via Atlassian add-ons are also available to qualified institutions at the same reduced price. See more here:
How do community licenses work?
Atlassian supports organizations that seek to do good in the world. Charitable organizations can apply for no-cost Community licenses. Once a customer has a Community license for any Atlassian product, they can request additional licenses from Atlassian sales representatives, including Community licenses for add-ons they obtain through the Marketplace.
Your customers can apply for an Atlassian Community license here:
Customers with an existing Community license for any Atlassian product, should request a Community license for your add-on by emailing email@example.com.
How do open source licenses work?
apply for no-cost Open Source licenses. Approved organizations can request Open Source licenses for paid via Atlassian add-ons by contacting Atlassian sales representatives. These representatives validate and issue Community licenses.Atlassian wants to support the Open Source community that has helped Atlassian come so far, open source projects can
Can customers use developer licenses for my add-on?
The license types between the add-on and host application must match. That is, an add-on with a developer license only works in a host application that also has a developer license. The same applies to production licenses—a host application with a production license only takes add-ons that also have production licenses. If an add-on license type doesn't match its host application, the Universal Plugin Manager reports a license error status of "Incompatible with product license (wrong type)" for that add-on.
Find out how to create developer licenses here:
Can I generate license for my add-on?
At this time, there is no automatic way to issue yourself a license to your Marketplace add-on. We may add this in the future. In the meantime you can use Marketplace Promotions to create any 100% discount licenses you need for internal purposes. Promotions are found on your Manage vendor account page on marketplace.atlassian.com.
Can my customer purchase more than a year of maintenance?
Marketplace customers can purchase maintenance for one, two, or three years.
Can maintenance license renewal dates be synchronized across all of a customer's paid via Atlassian add-ons?
Yes. Find out more here: http://www.atlassian.com/licensing/purchase-licensing#softwaremaintenance-5
Can I convert my old licensing system to the Atlassian licensing system?
Which product versions does the licensing solution support?
The licensing solution provided by the Universal Plugin Manager (UPM) supports the following products:
- Confluence Cloud
- Confluence Server (3.1 and newer)
- JIRA Cloud
- JIRA Server (4.1 and newer)
- Bitbucket Server (1.0 and newer)
- Bamboo Server (2.6 and newer)
- FishEye/Crucible (2.4 and newer)
Can I get a license ID via the PluginLicense API?
Yes, you can. Use the
PluginLicense.getSupportEntitlementNumber() method to get this value.