Here's how to add your listing to the Marketplace:
Atlassian reviews and approves new app listings before they appear on the Marketplace, but new versions don't require approval.
If you're listing a cross-product paid via Atlassian app, repeat steps 3–6 for each supported product. Each supported product requires a separate listing. However, if you're listing an app that works for one product across different hosting models (like Confluence Cloud and locally hosted Confluence instances), you should list these apps together as different versions of the same app. Read more here.
Check out our approval guidelines.
The Top Vendor program recognizes vendors who have exemplary app quality, reliability, and customer support. In addition, if you sell at least one paid via Atlassian app in the Marketplace, you can apply to become a Top Vendor. Check out our Top Vendor program requirements.
In the Atlassian Marketplace, the app level encapsulates information that doesn't change. For example, the name, the vendor, the key, etc. wouldn't change between app 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.
You can edit directly from the Marketplace:
The Atlassian Marketplace uses a full-text search of the app title, description, and vendor name. It also indexes the release notes you enter in each app version. You can optimize your search results by changing the content in these fields.
Atlassian periodically chooses to feature a few apps. We look at general usefulness and popularity, determined by how many active product instances have your app installed. Featured apps appear as the Staff Picked category in the app list. In addition, we present targeted banner images in the carousel of the Atlassian Marketplace in the Find new apps page in the Universal Plugin Manager (UPM).
You specify product compatibility with your app in the Create new add-on form. When Atlassian releases minor versions that outpace your app's compatibility, we automatically update this information for you. For example, if your app is compatible with Confluence version 6.2, and version 6.3 comes out, we assume your app 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 app is compatible, you can update your listing and we'll move forward with minor releases as usual.
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.
Only if your app 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.
Free and paid via vendor cross-product apps can be listed by specifying all the compatible applications when submitting the app version.
Paid via Atlassian app listings are product-specific in the Marketplace. List your app for each host product individually, and differentiate each app using specialized app keys. All other assets and artifacts can be left the same.
Here's an example of a modified app key for Jira:
Here's an example of a modified app key for Confluence:
Customers will need to license each separately.
Just one listing is enough. If your Atlassian Connect app does the same thing behind the firewall as it does in the cloud, keep it simple with a single listing. Even if your app 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 app separately.
Here's how an app with two hosting models can share a single listing:
Once both hosting models are approved, your public listing reflects both hosting models.