Changelog

We've updated the payment method for US-based bank accounts of Marketplace Partners from Wire to ACH (Automated Clearing House) transfers.

Atlassian previously announced that customer general availability (GA) for multi-instance pricing would move to the fourth quarter of 2025. We are pleased to share that, while GA is still planned for Q4, we have launched a closed Early Access Program (EAP) with customers. This EAP will help us ensure we deliver a high-quality, robust feature.

In order to help Marketplace Partners accommodate larger customers, Marketplace cloud app pricing will be adjusted to match parent product pricing. We increased the number of users that customers can license on Jira Cloud from 50,000 to 100,000 on Jun 26, 2025

Beginning Jul 9, 2025, the pricing tiers for Jira cloud apps will be increased up to 100,000 users, a 100% increase from the previous limit of 50,000 users, with the following new pricing tiers added: 50,001 - 60,000 60,001 - 70,000 70,001-80,000 80,001-90,000 90,001-100,000 .

While version 3 of the Marketplace Review APIs is still under development, we’re releasing the documentation for these reporting APIs early to help you prepare for the upcoming changes. This release includes a preview of the API documentation schema and examples of API requests and responses.

To ensure smooth transition with the upcoming changes, we recommend to review the API documentation to understand and prepare for the upcoming changes.

Following its review release, we are excited to announce that the Marketplace V3 reporting APIs are now generally available. This means that these reporting APIs are now fully operational and can begin utilizing these APIs in production environments.

For more information, see V3 Reporting APIS.

To facilitate a seamless rollout of Jira 100K user tier, we will freeze set pricing updates for July 3rd - July 4th, 2025.

During the pricing freeze, new app submissions for approval will be blocked if they require pricing changes. However, apps with pre-set pricing can still be submitted for approval.

Time: 9:00 AM (July 3rd, 2025) to 9:00 PM (July 4th, 2025) in IST.

Atlassian is introducing the option for Marketplace Partners to use a standard, customizable end-user agreement starting on June 25th. Our goal is to help streamline and simplify the process of negotiating terms with customers during the procurement process.

Once the standard end user agreement is adopted, it will replace the link to your current End User License Agreement (EULA) on your app listing page. Learn more here.

As part of our ongoing efforts to enhance security and improve our services for Atlassian Marketplace partners and customers, we're pleased to announce an important update to the Continuous Scanning process for Marketplace Data Center (DC) apps.

What's Changing?

Previously, the Data Center Security Scanner was configured to scan only the latest version of Marketplace DC Apps. Given the higher adoption rate of our Long Term Support (LTS) versions of Data Center products and to ensure broader security coverage for our customers, we will now include not only the latest version of the apps, but also app versions that support the current and previous Data Center LTS versions.

Additional Updates

1. Increased Volume of Tickets in AMS: With the expanded scope of our continuous scanning efforts, we anticipate an increased volume of tickets in Atlassian Marketplace Security (AMS). To focus on risk reduction and workload management, while providing you with the best service possible, we will communicate the initial set of vulnerabilities in weekly batches according to severity/vulnerability class starting Jun 23, 2025. We will start with Critical vulnerabilities and continue with High, Medium, and Low. You can learn more about the severity levels in our Security Bug Fix Policy.

2. Expanded Scanning Tools: As part of our continuous scans, we will be employing three scanners to ensure comprehensive security coverage:

   • Malware Scanner

   • Software Composition Analysis (SCA) Scanner

   • 🆕 Static Application Security Testing (SAST) Scanner

Why This Matters

• Comprehensive Security Coverage: By expanding the scan to include app versions compatible with both current and previous Data Center LTS versions, we ensure that vulnerabilities in older, yet widely used, app versions are detected and addressed.

• Multi-Layered Security Analysis: Utilizing a combination of Malware Scanner, Software Composition Analysis (SCA) Scanner, and Static Application Security Testing (SAST) Scanner allows us to identify a wider range of potential security issues. This multi-faceted approach helps us uncover vulnerabilities related to malicious code, outdated libraries, and insecure coding practices, providing a thorough security assessment for your applications.

We believe these changes will significantly benefit our customers by providing enhanced security assurance and support. Thank you for your continued collaboration and commitment to maintaining high standards in the Atlassian Marketplace. If you have any questions or need further assistance, please do not hesitate to reach out to our support team.

We are introducing a new billing model: maximum quantity billing.

With maximum quantity billing, customers are charged for the highest number of seats they reach in a given month, and any seats added during the month are billed on a prorated basis. While Marketplace partners are not required to take any action, we recommend partners familiarize themselves with the sales type associated with charges that will appear in reporting for maximum quantity billing.

This model will modify the current per-user pricing structure for monthly Atlassian Marketplace cloud app subscriptions and will be rolled out to customers starting in early August, with full GA expected by the end of October.

For more details, please refer to this Quick reference guide.

We’ve published new documentation explaining how grace periods work for licenses. To help you programmatically identify grace period status, the getLicensesAPI now includes an inGracePeriod field.

This field enables you to determine if a license is:

• Currently in a grace period → inGracePeriod: Yes

• Was previously in a grace period, but is no longer → inGracePeriod: No

• Never had a grace period → inGracePeriod field will be absent

📝 Note: There are no UI changes associated with this update - the information is available only via API.

Following its Preview release, we’re excited to announce that the Runs on Atlassian program is now generally available.

This means that customers can now see the Runs on Atlassian badge for eligible apps on the Atlassian Marketplace. Similarly, customers can also filter for eligible apps.

Check out Runs on Atlassian documentation to know more about the program, as well as the eligibility requirements and the next steps you can take.

We’ve started the customer rollout for the Runs on Atlassian program. This means that some customers can now see the Runs on Atlassian badge for eligible apps on the Atlassian Marketplace and on the Connected apps page of Atlassian Administration.

To ensure a smooth transition, we’re progressively rolling this out to customers over the next few days. We’ll provide another update upon completion.

Check out Runs on Atlassian documentation to know more about the program.

We are removing the functionality for importing workflows from Marketplace apps. Customers won't be able to import workflows hosted in apps directly starting from 23 June 2025.

The workaround for https://developer.atlassian.com/platform/marketplace/knowledge-base/how-do-i-import-a-workflow-into-a-jira-cloud-instance/ will no longer be available.

Marketplace team has updated the logic for calculating the saleType provided via the transactions report.

To address the varied use cases regarding enhancements in pricing and packaging of apps on the Marketplace, we are transitioning from assessing sale type value based on the changes in user count from prior transactions. Instead, we will adopt a method that considers the relationship between the gross list price and the editions available. This new approach allows us to shift our focus from the variability in user count to a more comprehensive and inclusive rationale.

With this update in logic:

• The type of sale will be defined by the interplay between the gross list price and the editions offered. The gross list price represents the total amount a customer must pay based on the listed price, without accounting for any deductions or adjustments.

• We are introducing a new sale type referred to as DOWNGRADE. If there is a reduction in the gross list price compared to previous transactions, or if the edition is downgraded while the gross list price remains unchanged, the transaction will be classified as a downgrade.

• The same will be reflected in the user experience for partner reporting

These changes will be applicable to transactions from May 15, 2025. We encourage partners to read the quick reference guide here to know more about this change.

Atlassian has made the decision to move customer GA for multi-instance pricing to the fourth quarter of 2025.

While we recognize the significance of this decision, we are confident that it is a crucial step towards developing the most streamlined and efficient processes for our partners and shared customers.

We will share more details on a more precise GA date at a later time.