Last updatedJun 5, 2020

Rate this page:

App approval guidelines

After creating and testing your app, your next step is to submit it for approval. To uphold standards of quality and reliability that our customers expect, all publicly listed apps are subject to an approval process.

Which apps are subject to the approval process?

  • Publicly listed, new apps
  • Payment model changes: For example, if your app changes from free or paid-via-vendor to a paid-via-Atlassian app.
  • Hosting changes: If you add a version that uses a different hosting model. For example, if you have a download/behind-the-firewall app, and add a version for Atlassian-hosted cloud products.

If an earlier app version is already approved, routine version updates are exempt from the approval process except in the above cases.

Approval process

Approval times vary depending on current volume and the Marketplace team’s availability, submissions fall into an internal queue which the Marketplace team works through chronologically as they come in. Our team checks a range of requirements for your app, like if it installs properly and has documentation. It's not uncommon to experience a few rounds of the approval process. To avoid unnecessary updates and resubmissions, make sure your app adheres to the guidelines on this page. If you believe your approval is taking too long, feel free to check in via a question to our team.

  1. Log in to with your partner account.
  2. Click Publish a new app from the profile menu in the upper right.
  3. Fill out the app submission form and upload related assets. 
  4. Accept the Marketplace Partner Agreement, and submit your app.
  5. Our Marketplace team automatically creates a Jira issue to track the approval process. Create an account for Ecosystem Jira so you can track the status. Use the same email as your partner profile.
  6. You'll be notified via email that your submission was successful, and receive a URL to track the approval process. You can click View workflow in the details section of your Jira issue to see the submission status.
  7. Once approved, your Jira issue is closed and your app is published to the Marketplace.

Criteria for all apps

All apps, free or paid, for Cloud or Server instances, need to meet the following criteria: 

  • Provide marketing assets: Provide marketing assets like a logo, banner, and screenshots as defined by Building your presence on MarketplaceDeclare these assets in the app descriptor. This is recommended but not required for free apps.
  • Reasonable pricing: Your paid app should be reasonably and competitively priced.
  • Performs as described: Your app does what it advertises.
  • Provide documentation: Your listing should reference documentation that describes how to set up and use your app.
  • Doesn't break the host product UI: The UI of the host product should be functional and intact when your app is installed. If the UI breaks, your app will be rejected.
  • Doesn't degrade host product performance: Your app shouldn't significantly impact the host product performance.
  • Doesn't infringe Atlassian trademarks: Trademark infringement is an automatic rejection, so be sure to read our brand guidelines for Marketplace Partners before submitting your app. This includes visual assets as well as naming conventions. For example, Jira App X would be rejected, but App X for Jira would be approved.
  • Available source code for open-source apps: If your app is open source, ensure your source is publicly available. We recommend a hosting site like Bitbucket. Include a license file in your source code that matches what you report in the Marketplace.
  • No advertisements: Your listing shouldn't contain advertising for other apps, products, or services. You can mention paid versions of the same app or products that complement your app. In the host product, your app should abide by the same rules. Reminders for upgrades, complementary products, or additional features are acceptable. We recommend placing these reminders in configuration screens.
  • Free and paid external service elements are clear: If your app listing is free, ensure your app provides some useful function in the Atlassian parent product 'as is'. If your app requires a separate third-party account this must be clear. If a separate third-party account is required and is subject to payments and licensing, ensure this is clear. We recommend in most cases these apps be listed as paid via vendor, unless your app provides some useful functionality without the third-party account.

Additional criteria for paid via Atlassian, server apps

Your paid via Atlassian, server app adheres to the criteria listed for all apps, plus:

Additional criteria for cloud apps

Your cloud app adheres to the criteria listed for all apps, plus:

Rate this page: