Browse, install, evaluate, and buy add-ons for Atlassian Products
General Marketplace Questions
- 1. What is Atlassian Marketplace?
- 2. What is an add-on? Is it a plugin?
- 3. How are add-ons reviewed?
- 4. How do I get an account so that I can try or buy an add-on?
- 5. How do I know if an add-on is a good product?
- 6. Which add-ons does Atlassian support?
- 7. Can add-ons make my application slower?
- 8. If I have an issue with an add-on, should I contact Atlassian?
- 9. Why would I disable an add-on? How do I disable one?
- 10. Where do I go to ask a question or get support for my add-on?
- 11. What is add-on archiving?
- 12. Which countries can purchase add-ons from the Marketplace?
Licensing and Pricing
- 1. Which license do I choose when purchasing an add-on?
- 2. What is enterprise pricing?
- 3. Can I get an extension for my Marketplace add-on evaluation?
- 4. Do I need to purchase multiple licenses for multiple instances of the Atlassian product?
- 5. Where do I get the license keys for my new add-on?
- 6. When and why do I need to renew my license?
- 7. Am I eligible for academic pricing?
- 8. How are license upgrade prices calculated?
- 9. How do I get an Atlassian Community license for an add-on?
- 10. What are Atlassian Open Source and Atlassian Classroom licenses?
Atlassian Marketplace is a one stop shop for add-ons to Atlassian products. We built it to make it easier to discover, install, evaluate, and buy awesome additions to JIRA, Confluence, and our DVCS and developer tools.
This FAQ below should answer many of your questions - if not please contact our Sales Team.
General Marketplace Questions
1. What is Atlassian Marketplace?
The Atlassian Marketplace replaced the old Atlassian Plugin Exchange. The Marketplace is a new system that makes it easier for vendors to sell their add-ons and easier for you to find and install them.
2. What is an add-on? Is it a plugin?
In the past, Atlassian used the term plugin to refer to any product a customer could use with an Atlassian host product such as JIRA. The term plugin doesn't work for every product. We think add-on fits.
Plugins are small pieces of code that you (or your administrator) can install into an Atlassian application to enhance or change the application's default functionality. Other add-ons can be installed into third-party products and then integrated with Atlassian products. For example, the JIRA Connector for Jama Contour installs in the Contour application and connects to JIRA.
Sometimes add-ons are written by Atlassian, sometimes they are written by someone else in the Atlassian community. You can even write one yourself. The Marketplace has over a thousand free and paid add-ons available. You can find detailed information, version histories, screenshots, pricing, ratings, comments, reviews, and much more on the Marketplace.
Add-ons will change the way your application behaves, potentially for the worse. You install add-ons at your own risk, and only some of them are supported by Atlassian. You can enable, disable, and uninstall add-ons at any time from the Administration section of your Atlassian product.
3. How are add-ons reviewed?
Atlassian checks the entries in the Atlassian Marketplace to ensure the information provided is as complete as possible. However, we do not actively monitor or guarantee any code posted in this space. If you find dangerous or malicious code posted here, please contact us immediately.
4. How do I get an account so that I can try or buy an add-on?
5. How do I know if an add-on is a good product?
Look at the reviews that other users have written, and check the number of downloads for a measure of an add-on's popularity. Other users look for information such as:
- how frequently an add-on is released
- screen shots or video to check functionality
- user agreements (EULA)
You can also ask a question in Atlassian Answers.
6. Which add-ons does Atlassian support?
Look on the right-hand side of any add-on page in the Atlassian Marketplace to see the add-on's support information. This includes the add-ons that Atlassian creates.
7. Can add-ons make my application slower?
Yes. Once installed, add-ons have great power inside the application. Sometimes, they can cause performance or other problems. That is why it is important that you learn all you can about an add-on.
You can evaluate an add-on in a staging environment before deploying it in production. You can also use the customer reviews to learn what other users have to say. Visit the website of the add-on vendor and review any support materials they have.
If you suspect an add-on is causing a problem in your Atlassian application, try disabling the add-on to see if the problem goes away.
8. If I have an issue with an add-on, should I contact Atlassian?
In general, no. To find the support contact for an add-on:
- Browse to the add-ons's page on the Atlassian Marketplace.
- Scroll to the add-on details on the right hand side of the page.
- Look for the Supported by item in this section.
This item tells you how to get support.
If the add-on is supported by Atlassian, please file a ticket in our Support System. If the add-on is unsupported, we encourage you to post questions in our Forums. If you encounter any add-ons that you believe to be malicious, please contact us immediately.
If you have a question about purchasing, renewals, or upgrades for paid-via-Atlassian add-ons, please contact our sales team.
9. Why would I disable an add-on? How do I disable one?
When you install an add-on, it has full access to change the internals of your application. Sometimes add-ons can have unintended side-effects. They might slow things down, or you might discover a problem. If so, it's easy to disable or uninstall an add-on.
|Product||Where to go for more information|
|JIRA||Managing JIRA's Plugins|
|Confluence||Installing Plugins and Macros|
10. Where do I go to ask a question or get support for my add-on?
On the Atlassian Marketplace, look for support links on the right side of every add-on page, or if there is no support link, then look for a link to a JIRA instance where you should file a ticket. Writing an add-on review is not the best way to get support.
11. What is add-on archiving?
To keep the focus on current, relevant add-ons, the Atlassian Marketplace regularly archives add-ons that are out-of-date or, for any other reason, no longer relevant on the Marketplace.
Archiving prevents the add-ons from appearing in search results or in add-on browsing lists. The Marketplace archives add-ons automatically if the time since the end-of-life of the latest version of the Atlassian application it supports is greater than one year.
If you already have a license for the add-on, you can still download the add-on from its Marketplace listing and use it. However, new licenses for the add-on are not available. Contact the vendor to inquire about an updated version of the add-on.
12. Which countries can purchase add-ons from the Marketplace?
The Atlassian Marketplace will help vendors collect the appropriate sales and VAT taxes. We are able to sell to customers everywhere, with the following exceptions:
- Trade embargoed countries subject to United States export restrictions
We're constantly working to expand access to the Marketplace. As we continue to work on resolving tax discrepancies, customers from the countries listed above will become eligible to purchase from the Marketplace. In the meantime, we have a list of Atlassian Experts in the approved regions that you may contact directly for your purchase.
For more information, please visit our Developer FAQ.
Licensing and Pricing
1. Which license do I choose when purchasing an add-on?
The Atlassian host application (for example, JIRA, Confluence, etc.) license tier determines the license type you need for an add-on that is paid-via-Atlassian. For example, if you are installing an add-on into a JIRA with 25-user license, you must purchase a 25-user license for the add-on, even if fewer users will actually use it.
IMPORTANT: If you do not purchase a license that matches your Atlassian application license, your add-on will not work.
Prior to and including February 2012 is the designated legacy time period. If you purchased your Atlassian host product within this legacy time period, the same tiers continue to be available for your add-on.
- The JIRA tiers are 10, 25, 50, and 100 users. The legacy unlimited tier was 100+ users.
- The Confluence legacy tiers are 10, 25, 50, 100, 500, and 2000 users. The unlimited legacy tier was 2000+ users.
There are no enterprise licenses prior to and including February 2012.
Note: When purchasing Marketplace add-ons for a Confluence license with Clustered Nodes, you must purchase a separate add-on license for each node. For example, if you have Confluence with 3 Clustered Nodes, you must purchase 3 add-on licenses (one for each node) in order to use the add-on.
2. What is enterprise pricing?
As of March 2012 and later, Atlassian offers enterprise pricing tiers for larger organizations. Enterprise pricing offers a different level of support. If you have JIRA Enterprise or Confluence Enterprise, you must purchase at the enterprise level tier for your paid-via-Atlassian add-on.
3. Can I get an extension for my Marketplace add-on evaluation?
You can extend your Marketplace add-on evaluations up to five times, for a total of six months. You can do this by generating a new evaluation license key on the add-on's Atlassian Marketplace page and copying that license key into the manage add-on screen in the host product's Administration section.
Alternatively, if you remove your expiring evaluation license from the add-on inside the host product, the "Free Trial" button will be re-enabled and you can generate a new evaluation license from there.
Please contact the Atlassian ecosystem team if you have a question about extending your evaluation license.
4. Do I need to purchase multiple licenses for multiple instances of the Atlassian product?
Yes. Add-ons are only licensed for a single instance of an Atlassian product. You must purchase additional licenses if you intend on installing the add-on in multiple production instances.
When purchasing Marketplace add-ons for a Confluence license with Clustered Nodes, you must purchase a separate add-on license for each node. For example, if you have Confluence with 3 Clustered Nodes, you must purchase 3 add-on licenses (one for each node) in order to use the add-on.
Note that you can use developer licenses to deploy non-production installations of add-ons to assist with development and testing before pushing your add-on live. For more information, see "Can customers use developer licenses for my add-on" on the Licensing and Paid-via-Atlassian Listings Developer FAQ.
5. Where do I get the license keys for my new add-on?
You receive access to license key(s) and any applicable source code after the successful receipt and processing of your payment. Once the system receives a payment, it sends a confirmation email to you that includes instructions on how to access the license key and any applicable source code are provided in the confirmation email.
You can log into My Atlassian to retrieve your key. Just as with Atlassian products, any purchase you make through the Marketplace is listed in your My Atlassian account.
6. When and why do I need to renew my license?
Twelve months after the purchase date of a paid-via-Atlassian add-on version, support for your add-on stops. You are also no longer able to update to new versions. You must renew your license to continue to have access to support and updates after 12 months.
7. Am I eligible for academic pricing?
Academic pricing is available to qualified academic institutions for paid-via-Atlassian add-ons. Academic licenses are not eligible for the volume renewal discount.
The following organizations are eligible for an Atlassian Academic License:
- Educational institutions: Public or private K-12, vocational schools, correspondence schools, junior colleges, colleges, universities, or scientific or technical schools that are accredited by a national accrediting agency.
- Administrative offices & boards of education: Provincial, district, regional, national and state administrative offices and authorities of the Educational Institutions defined above.
- Public libraries
- Home-school programs
- Research institutes that are affiliated with an accredited university.
- Teaching hospitals that are affiliated with an accredited university.
- Training and teaching organizations that are accredited by a statutory government qualifications body.
Proof of accreditation or affiliation may be required when ordering an Atlassian Academic License for your add-on. Academic pricing is always half the cost of commercial pricing. In the same manner, academic renewal pricing is always half of commercial renewal pricing.
8. How are license upgrade prices calculated?
You can upgrade licenses at any time from a lower tier to a higher tier. Upgrades include 12 months of maintenance commencing from the date payment is processed. This will override any existing maintenance period.
The price to upgrade from a lower to higher license tier is calculated based on Atlassian's formula, as seen here for JIRA. MyAtlassian automatically calculates the appropriate price based on the license upgrade formula when you add the license upgrade to your shopping cart.
9. How do I get an Atlassian Community license for an add-on?
Atlassian supports organizations that seek to do good in the world. If yours is a charitable organization, you can apply for a no-cost community license. Once your organization has a community license for any Atlassian product, you can request additional licenses from Atlassian sales representatives, including community licenses for add-ons you obtain through the Marketplace.
Request an Atlassian Community license.
If you have an existing community license for any Atlassian product, you can contact us to request additional Atlassian Community licenses for other products and add-ons.
10. What are Atlassian Open Source and Atlassian Classroom licenses?
Atlassian offers a number of free licenses for individuals and organisations involved in open source or classroom efforts. Once your organization has an open source or community license for any Atlassian product, you can request additional licenses from Atlassian, including commuity licenses for add-ons you obtain through the Marketplace.
Once your organization is approved for either of the above license types, you can contact us to request additional licenses for any paid-via-Atlassian add-on.