Last updated Oct 27, 2023

Submit your Data Center app to the Atlassian Marketplace

Prepare to share or sell your Data Center (DC) app on the Atlassian Marketplace.

Before you publish your app, you'll need to:

  1. Start, complete, and submit the technical review for your Data Center app.
  2. Test your app and share the results in the comment section of your technical review ticket.
  3. Provide the results of your security check and generate your dependency tree.
  4. Attach your app's .jar file to your technical review ticket.
  5. Update your app descriptor.
  6. Create your Marketplace listing. You'll need the technical review ticket created in Step 1.

Before your Data Center app launches on Marketplace, both your technical review and Marketplace listing need to be approved.

If you have any questions about Data Center or Marketplace, ask our team.

Server to Data Center apps – before your technical review

If you’re releasing a Data Center version of a server app, before starting your technical review you’ll need to notify your customers.

Three months before launch, your release notes need to outline that:

  • You plan to launch a Data Center approved version of your existing server app
  • Your customers need to purchase a Data Center app license for their next app renewal

One month before launch you’ll need to contact your customers to:

  • Notify them of your Data Center app launch date
  • Guide them through the steps to renew or migrate their license

For more information, check out this thread in the Developer Community.

If you need access, submit a request to view Partner-only content.

Data Center apps have different guidelines to Atlassian Server apps. Check the guidelines.

1. Complete the technical review

To list your Data Center app on Marketplace, you need to complete a technical review.

The technical review helps us make sure your app meets the performance and stability requirements of our largest Data Center customers.

Start your technical review ticket.

Within the technical review ticket:

  1. Complete the form with your app's support, functionality, and security details.
  2. Submit the completed review form.
  3. Test your app's performance and add the results to the ticket.
  4. Provide the results of the security check with the dependency tree.
  5. Attach your app’s .jar file.

You’ll hear from our team within 5–10 business days.

If we have any questions about your submission, we'll ask you in this ticket.

While your technical review is being checked, you're welcome to start your Marketplace listing (Step 4). In the Marketplace listing, you'll be asked to provide your Technical review issue key. This is the tracking number on your technical review ticket. For example, DCHELP-123.

If your app works with more than one Atlassian product, you'll need to complete a technical review ticket for each.

Learn more about the Data Center app approval process.

Test your app against major databases:

In your technical review there's a section related to testing your app against the major databases:

  • PostgreSQL
  • MySQL
  • Microsoft SQL Server, and
  • Oracle

Testing against the supported databases is still required even if you access databases directly or through active objects. It's important to test functionality that involves any operation with the database.

If your app does not access databases directly or through active objects:

  • Check the successful installation of the application
  • You do not need to run Performance and Scale tests against all databases
  • You need to confirm that your plugin can work independently against the database type

For non-installable apps

If you have a non-installable Data Center app, you also need to submit a technical review.

Some differences are:

  • Security checks are not needed
  • Additional questions about app performance are asked in the technical review ticket comments
  • If your app affects product performance, you may be asked to run tests and share the results

Annual review for Data Center apps

Once your app's initial technical review is approved, each year you'll need to submit an annual review.

You can access and complete this within your technical review ticket.

In the annual review, you'll need to:

  • Outline any functionality changes in your app
  • Run performance, scale tests and security checks
  • Share your results in the technical review ticket

One month before your Annual Review date you'll receive an email reminding you to:

  • Complete the annual review survey via your initial technical review ticket
  • Provide the results of the security check with the dependency tree
  • Use the latest version of your app for all tests

Two weeks after the due date, if you have not completed the Annual Review you'll receive an email reminder.

If Atlassian does not hear back from you, the team will begin to remove your app from Marketplace.

2. Test your app's performance at scale

After creating your technical review ticket in Step 1, use it to add details about how your app performs at scale.

It's important to check how your app handles the types of user load our biggest customers typically see.

Use the Data Center App Performance Toolkit

For performance and scale testing we recommend you use the Data Center App Performance Toolkit.

Each Atlassian product has a different toolkit:

To run the toolkit:

  1. Install the relevant toolkit on a testing host.
  2. Add your app-specific actions to the toolkit.
  3. Set up an enterprise-scale Data Center deployment on AWS.
  4. Run the tool to collect performance and scale data.
  5. Document the results on your technical review ticket.

Use your own testing environment

You can use your own testing environment if:

  • You already have one
  • You prefer to use a different set of testing tools

Test and document how your application performs in a Data Center deployment with one, two, and four application nodes.

Learn more about performance and scale testing requirements.

Lucene index test for JIRA

If you're submitting a Jira or Jira Service Management app, you'll need to conduct a Lucene Index timing test.

This involves conducting a foreground re-index on a:

  • Single-node Data Center deployment (with your app installed)
  • Dataset that has 1M issues

We recommend the Data Center App Performance Toolkit to conduct this test. It ships with an appropriate dataset for testing. Without an app installed, it takes about 50minutes.

Upon completing the index:

  1. Screenshot the acknowledgment screen displaying the re-index time.
  2. Attach the screenshot to your technical review ticket.

3. Security check and dependency tree

You can use any tool of your choice to provide the results of security scanning for third party dependencies vulnerabilities.

You'll need to do this for:

  • Your initial Data Center app submission
  • Each Data Center app annual review

Your security scanning report must be free of critical and high-severity security vulnerabilities in third party dependencies bundled with the app.

For the dependency tree:

  1. Generate it for your app.
  2. Attach the results to your technical review ticket.
  3. We'll sanity check for third party dependencies vulnerabilities with the Data Center (DC) Apps Security Scanner.

If any critical or high-severity security vulnerabilities are found:

Check Regular security scanning for more details.

You'll also be asked to attach the .jar file for the version of your app you’d like to release.

4. Update your app descriptor

Before you submit your app to Marketplace, you'll need to add Data Center compatibility to your app descriptor (atlassian-plugin.xml).

The plugin-info section will need to contain:

<param name="atlassian-data-center-status">compatible</param>
<param name="atlassian-data-center-compatible">true</param>
  • The atlassian-data-center-status parameter indicates to Marketplace and Universal Plugin Manager (UPM) that you've submitted an app for technical review.
  • The atlassian-data-center-compatible parameter was previously used to indicate Data Center compatibility. It's included for backward compatibility with older UPM versions.

Here's an example of a generic plugin-info block with these parameters:

    <vendor name="${}" url="${project.organization.url}" />
    <param name="atlassian-data-center-status">compatible</param>
    <param name="atlassian-data-center-compatible">true</param>

If your app is an OBR artifact with bundled dependencies, include the above parameters in both the:

  • Main app descriptor
  • Descriptors for any dependencies

Define your artifact type

Single Artifact

No Action Required

Optionally, we'd like you to update your app descriptor (atlassian-plugin.xml) to contain the following parameters in the plugin-info section for your artifact:

<param name="plugin-type">both</param>

Separate Artifacts

You'll need to update your app descriptor (atlassian-plugin.xml) to contain the following parameters in the plugin-info section for your server and Data Center artifact:

Server Artifact:

<param name="plugin-type">server</param>

Data Center Artifact:

<param name="plugin-type">data-center</param>

5. Start your Marketplace submission

After starting your technical review, you can start your app's Atlassian Marketplace listing.

Your Data Center app Marketplace submission:

  • Can still be drafted while your technical review is being approved.
  • Will require an approved technical review before being launched
  • Can take 5-10 business days for our team to process

How to start your Marketplace submission:

  1. Log in to the Atlassian Marketplace with your partner account.
  2. Select Publish a new app from the profile menu in the upper right.
  3. Select the Vendor account you'd like associated as the app owner.
  4. Upload your App file.
  5. Enter your App name.
  6. Select Next: Make public.
  7. Next, follow the screens to complete your Marketplace submission. You'll be asked to provide your Technical review issue key from the review ticket.

If you have any questions, ask our team.

List a Data Center version of your server app

If you're submitting a Data Center version of your server app to Marketplace, note:

Server and Data Center compatible versions of your app share:

  • A single Marketplace listing
  • The same app details page

You can use a single artefact for both server and Data Center:

  • When you upload it to Marketplace, select whether the version should be compatible with:
    • Data Center and server, or
    • only Data Center

If you use a single, shared artefact for server and Data Center, both versions need to have the same payment model:

  • Data Center apps can be either:
    • Free
    • Paid via Atlassian, or
    • Paid via Vendor

How to list the Data Center version of your server app to Marketplace:

  1. Log in to the Atlassian Marketplace with your partner account.
  2. Select Manage vendor account from the profile menu in the upper right.
  3. Select the name of the app you're adding a Data Center-compatible version for.
  4. Select Create version.
  5. Upload your artefact.
  6. Select if your new version should be compatible with both Data Center and server, or just Data Center.
  7. Follow the steps to submit your app. Provide a link to your technical review ticket.

Data Center updates

We continue to develop and release:

  • Performance Testing tools
  • Benchmarks on performance
  • Guidelines on monitoring
  • Guidelines on improving the performance of Atlassian Data Center products

With any updates, we'll make the relevant changes to our processes and documentation. It's our priority that you have the latest and most accurate guidance.

Rate this page: