Listing & managing add-ons
How do I list my add-on in the Marketplace?
Here's how to add your listing to the Marketplace:
- Log in with your vendor credentials.
- Click Create add-on from the profile menu (upper right).
- If this is your first add-on submission, follow the prompts to register your vendor and contact details.
- Click the Create add-on button.
- Fill out the form and upload your branding assets.
- When ready, click Submit for approval.
Atlassian reviews and approves new add-on listings before they appear on the Marketplace, but new versions don't require approval.
If you're listing a cross-product paid via Atlassian add-on, repeat steps 3-6 for each supported product. Each supported product requires a separate listing. However, if you're listing an add-on that works for one product across different hosting models (like Confluence Cloud and locally hosted Confluence instances), you should list these add-ons together as different versions of the same add-on. Read more here.
How do I make sure my add-on gets approved?
Check out our approval guidelines.
How do I get Atlassian Verified status?
Atlassian Verified vendors uphold Atlassian standards for add-on support, Marketplace traction, and product compatibility. If you sell at least one paid via Atlassian add-on in the Marketplace and meet Verified benchmarks, you can apply to become a Verified vendor. Check out our Verified program requirements.
What's the difference between add-on level and version level information?
In the Atlassian Marketplace, the add-on level encapsulates information that doesn't change. For example, the name, the vendor, the key, etc. wouldn't change between add-on versions. The version is a downloadable artifact (usually a JAR file) that represents a single release. Each version can have different screenshots, release notes, and compatibility information.
How do I edit an add-on listing?
You can edit directly from the Marketplace:
- Log in to the Atlassian Marketplace.
- Click Manage vendor account from the profile menu (upper right).
- Select the add-on you want to modify from the list.
- Make and save your changes.
How do I make sure my add-on appears in search results?
The Atlassian Marketplace uses a full-text search of the add-on title, description, and vendor name. It also indexes the release notes you enter in each add-on version. You can optimize your search results by changing the content in these fields.
How do I get my add-on featured in the UPM?
Atlassian periodically chooses to feature a few add-ons. We look at general usefulness and popularity, determined by how many active product instances have your add-on installed. Featured add-ons appear as the Staff Picked category in the add-on list. In addition, we present targeted banner images in the carousel of the Atlassian Marketplace in the Find new add-ons page in the Universal Plugin Manager (UPM).
What happens to my add-on compatibility when Atlassian releases new product versions?
You specify product compatibility with your add-on in the Create new add-on form. When Atlassian releases minor versions that outpace your add-on's compatibility, we automatically update this information for you. For example, if your add-on is compatible with Confluence version 4.3, and version 4.3.2 comes out, we assume your add-on will still work and update your listing accordingly. This is also true for beta versions.
When a major version is released, we leave it up to you as the developer and vendor to check compatibility. After you've confirmed that your add-on is compatible, you can update your listing and we'll move forward with minor releases as usual.
What if somebody posts an inappropriate review?
You can flag reviews as inappropriate, and our team will take a look. We also use spam-fighting software to prevent as many inappropriate reviews as we can. However, sometimes users post reviews that are well-intended, but contain incorrect information. In cases like these, you can respond to the review on the page to set the record straight, or email the reviewer directly.
Do I need to share my source code?
Only if your add-on is open-source. You can use Bitbucket to host your code.
That said, we find that sharing our code with customers increases their trust in our products, even though they're not open-source. We encourage you to share your source code with customers whenever possible.
How do I list a cross-product add-on?
Free and paid via vendor cross-product add-ons can be listed by specifying all the compatible applications when submitting the add-on version.
Paid via Atlassian add-on listings are product-specific in the Marketplace. List your add-on for each host product individually, and differentiate each add-on using specialized plugin keys. All other assets and artifacts can be left the same.
Here's an example of a modified plugin key for JIRA:
Here's an example of a modified plugin key for Confluence:
Customers will need to license each separately.
If my add-on has the same functionality in server & cloud instances, do I need two listings?
Just one listing is enough. If your Atlassian Connect add-on does the same thing behind the firewall as it does in the cloud, keep it simple with a single listing. Even if your add-on uses different mechanisms to solve the same problem, use a single listing on the Marketplace site. Though you'll use a single listing, this listing requires two approvals. Our Marketplace team approves both the downloadable and hosted version of your add-on separately.
Here's how an add-on with two hosting models can share a single listing:
- Create a single listing for one hosting model – Server or Cloud, it doesn't matter.
Your add-on enters our Marketplace approval queue.
- Click Add version and add the other hosting model as another version of your add-on.
This version of your add-on, even if it has the same functionality, also enters our approval queue.
Once both hosting models are approved, your public listing reflects both hosting models.