Prepare to share or sell your Data Center (DC) app on the Atlassian Marketplace.
Before you publish your app, you'll need to:
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.
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:
One month before launch you’ll need to contact your customers to:
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.
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:
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.
In your technical review there's a section related to testing your app against the major databases:
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:
If you have a non-installable Data Center app, you also need to submit a technical review.
Some differences are:
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:
One month before your Annual Review date you'll receive an email reminding you to:
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.
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.
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:
You can use your own testing environment if:
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.
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:
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:
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 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:
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.
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:
1 2<param name="atlassian-data-center-status">compatible</param> <param name="atlassian-data-center-compatible">true</param>
atlassian-data-center-status parameter indicates to Marketplace and Universal Plugin Manager (UPM) that you've submitted an app for technical review.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:
1 2<plugin-info> <description>${project.description}</description> <version>${project.version}</version> <vendor name="${project.organization.name}" url="${project.organization.url}" /> <param name="atlassian-data-center-status">compatible</param> <param name="atlassian-data-center-compatible">true</param> </plugin-info>
If your app is an OBR artifact with bundled dependencies, include the above parameters in both the:
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:
1 2<param name="plugin-type">both</param>
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:
1 2<param name="plugin-type">server</param>
Data Center Artifact:
1 2<param name="plugin-type">data-center</param>
After starting your technical review, you can start your app's Atlassian Marketplace listing.
Your Data Center app Marketplace submission:
How to start your Marketplace submission:
If you have any questions, ask our team.
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:
You can use a single artefact for both server and Data Center:
If you use a single, shared artefact for server and Data Center, both versions need to have the same payment model:
We continue to develop and release:
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: