Last updated Mar 13, 2025

Changelog

This changelog is the source of truth for all changes to the Marketplace that affect people publishing apps.

Posts are made in the Marketplace announcements category of the developer community when the changelog is updated. Subscribe to the Marketplace announcements category to get notifications.

13 March 2025

Announcement New DC pricing tiers for Jira and Confluence apps

We're introducing new app pricing tiers for up to 150,000 users for Confluence and Jira Data Center apps to better support our enterprise customers. You can update the pricing for the new tiers of your paid apps to ensure a seamless buying experience for customers. This change will take effect from March 17, 2025.

More details

Action required: Until you update the pricing, the per-user price of the new tiers will default to the current price of Unlimited tier (i.e. 40,001+ for Confluence DC apps and 50,001+ for Jira DC apps).

New User Tier Structure: New user tiers will be added from 50,000 (for Jira DC apps) and 40,000 (for Confluence DC apps) to 150,000 seats.

  • Each new tier will be in 10,000 seat increments

  • Unlimited tier pricing starts at 150,001 seats.

Note: Customers will be able to access and purchase new tiers on the same day.

Announcement New beta-headers for Jira and Confluence

On February 18th, we announced that we will begin enforcing REST API (Quota and Burst based) rate limits for all free Jira and Confluence apps on or after August 18, 2025 and that we have added additional headers to provide further transparency.

To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:

  • Beta-Retry-After

  • X-Beta-RateLimit-NearLimit

  • X-Beta-RateLimit-Reason

  • X-Beta-RateLimit-Reset

However, if you do receive headers without beta-, be advised that you are facing rate limits.

More details

Learn more about the new limits and headers for Jira here and Confluence here.

12 March 2025

Announcement Update to cloud churn, renewals and conversions computation

We have identified an issue in the cloud churn, conversion and renewal charts computation for paid apps with cloud and Data Center/Server hosting type. Specifically, Cloud churn, conversion and renewal was computed at the app level,

Meaning, if the Data Center/Server version of an app transitioned from paid plan to free plan for a certain time period, while the cloud version continued to be on paid plan, the cloud churn was not computed during that time. Consequently, this led to inaccuracies in the calculations for cloud churn, as well as renewal and conversion counts within the specified timeframe.


This issue has now been resolved, and effective Mar 12, 2025, Marketplace Partners can check accurate cloud churn, renewal and conversions computation in reporting section of Partner accounts as well as the following APIs

10 March 2025

Announcement New annual review tickets for Cloud Fortified and Data Center apps

Starting March 10th, 2025, we will create new annual review tickets for the Cloud Fortified Apps Program and Data Center apps. You now have up to 60 days to complete your annual reviews and you will receive ample reminders to ensure smooth renewal for your apps. You will also have access to the initial review and the previous years' annual reviews for as long as you are mentioned in the Request Participants field. Any changes to request participants will be replicated across all linked tickets to ensure access to your apps' historical annual reviews.

7 March 2025

Announcement Update on Discount amounts for Refund Transactions

We have identified an issue with the display of discount information for refund transactions. Up until today, refund transactions with discount amount for the following discount types:

  • EXPERT

  • MANUAL

  • MARKETPLACE_PROMOTION

were displayed inaccurately, failing to incorporate the summation of both Atlassian and Partner discounts.

  • This issue has been rectified, and the discount amount for each type is calculated as the sum of Atlassian and Partner discounts. We have backfilled the correct discount amounts for 11,000 records across Marketplace Partners. Partners can now access total discount value for the above discount types in the following APIs:

  • Implementation Date: The updated discount information will be accessible to partners commencing March 7, 2025. Partners can fetch updated records by the checking the lastUpdated field for the above mentioned APIs.

4 March 2025

Announcement App Bundles on Marketplace: Request for Participation in Pilot

We're excited to announce the launch of a pilot program for App Bundles on Marketplace!

We are looking for early adopters to work with us along the way.

What are bundles?

App Bundles represent a curated collection of multiple apps, offered to Marketplace customers as a cohesive package for purchase. Bundles enable partners to sell a collection of apps that work better together while simplifying decision-making and streamlining customer purchasing.

How will the pilot work?

The pilot will include the creation of a unified discovery experience of apps in the form of a single bundle listing. We will be using discount codes to provide a lower price point for apps in a bundle as compared to set pricing for individual apps

For the pilot, a select group of partners will be able to participate and create bundles on Marketplace. Interested in being a part of it? Please take a look at the expectations page and submit your interest via this form by Mar 14, 2025.

Partners are also encouraged to read this quick reference guide to get more information on the overall vision of app bundles from Marketplace.

3 March 2025

Announcement Correction to Free licenses data

We identified an error in the data display for Free Apps. Specifically, the maintenance start date was inaccurately updated to reflect the most recent changes in the license, which was not the accurate representation of the maintenance start date.

The issue has now been corrected, and therefore changes will be deployed on 3rd March 2025, impacting 1,039,402 records across Partners.

Partners can access the correct data by checking maintenanceStartDate in the license report APIs using the showLifeTimeFreeLicenses filter across:

  1. https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses?showLifeTimeFreeLicenses=true - Get life time free apps licenses data

  2. https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses/async/export?showLifeTimeFreeLicenses=true - Initiate async export of life time free apps licenses data

  3. https://marketplace.atlassian.com/rest/2/vendors/{vendorId}/reporting/licenses/export?showLifeTimeFreeLicenses=true - Export life time free apps licenses data

27 February 2025

Announcement Partners of Security Changes Coming June 2025

This announcement is for our upcoming security process & policy changes affecting Marketplace Partners going live in June 2025.

We intend to formally announce these changes to partners on: Feb 27, 2025

This initial announcement is intended to make partners aware of the changes coming in June, as well as provide the resources on DAC with specifics around what questions they will be required to answer in our updated App Onboarding and App Review processes.

This changelog ticket is just for our announcement and new/updated DAC pages. NO API or technical changes.

21 February 2025

Announcement Marketplace Platform Changes GA and Partner Implications

Atlassian Marketplace is transitioning to a scalable architecture by reengineering our monolithic data model and adopting a microservices-based approach to enhance reliability and scalability. With this, Marketplace partners will see some changes which will require adoption.

Key changes for Marketplace partners:

  • Transition from V2 APIs:

  • User experience enhancements: We are improving visual design of some of our experiences. These updates primarily focus on modernizing the tech stack and aligning with Atlassian Design Systems, replacing older designs.

For more information on implementation details and release dates, have a look at the Quick Reference Guide. Let us know your feedback as comments on the QRG.

More details

Why are we doing it?

To sustain and accelerate the growth of our Marketplace business alongside our partners, modernising our technology stack is essential. This modernisation will enable us to:

  • Deliver features faster and resolve incidents more efficiently, overcoming current limitations.

  • Build advanced capabilities that our partners and customers need.

  • Simplify system complexity caused by the legacy technology and architecture.

Call to Action

  • Plan your transition to new APIs: Start integrating the new API contracts into your systems to enhance performance, reliability, and capabilities. Allocate time in your development roadmap for testing and implementation once available.

  • Remove reliance on Deprecated APIs: Plan to stop using any deprecated APIs by their deprecation dates.

  • Stay informed: Monitor upcoming communications for final API contracts and transition timelines.

For more information on implementation details and release dates, see the QRG guide.

20 February 2025

Announcement Flexible pricing options for multiple instances

Multi-instance licensing is now live!The Atlassian Marketplace has introduced a new level of flexibility in app billing and licensing. This enhancement allows Cloud Enterprise customers to be charged based on the number of unique users of the app across multiple instances, irrespective of the number of product instances.

Customer GA is targeted for May 2025. The capability to set multi-instance pricing for apps is available from today, Feb 20, 2025. We recommend planning and setting your new pricing by May 15, 2025.

Key Points for Partners

  • Multi-Instance Pricing: Partners must offer multi-instance pricing for paid cloud apps alongside single-instance pricing, with flexibility to set different prices.

  • Existing Apps: Multi-instance pricing will be enabled by default, initially matching single-instance pricing.

  • Default Pricing: The pricing console will default multi-instance pricing to 1x of single-instance pricing, but partners can adjust this multiplier or edit fields as needed.

  • Customization: Partners can set multi-instance pricing as a price multiplier (≥1x of single-instance pricing) and edit pricing across different user tiers.

More details

Learn more here or via the developer documentation

19 February 2025

Announcement Feedback Reporting fix: Updated customer feedback for churn events

We have identified an issue within our system that resulted in the absence of customer feedback on churn events via the Feedback APIs between January to February 2025.

This issue has now been resolved, and consequently, 167,332 customer feedback records will be made available across all partners. These customer feedbacks were generated during the period from August 2020 to the present date. Effective Feb 20, 2025, partners will gain access to customer feedback regarding churn events from both historical and current feedback through reporting, as well as via the following APIs:

18 February 2025

Announcement Important notice: Updates to REST API rate limits

We have recently noticed an unusual increase in API usage. In order to maintain reliable services for both Atlassian customers and partners, we will begin enforcing more granular rate limits for Confluence and Jira APIs.

We will begin enforcing REST API (Quota and Burst based) rate limits for all free apps on or after August 18, 2025. We have added additional headers to provide further transparency. Please monitor header responses to see where you are at with regard to limits.

In some circumstances where apps are highly impacting the stability of our platform, we reserve the right to enforce the limits at an earlier date. We will notify your listed contact via email if you are impacted. Additionally, we are planning to bring clarity to rate limits across our platform infrastructure over the next year, including paid apps.

We recommend all customers and partners ensure they're not exceeding the rate limits so that they do not get impacted at a later date.

Learn more about the header responses and read relevant FAQs about rate limiting adjustments for Jira here and Confluence here.

Announcement Share your interest in the App Editions EAP

We're excited to announce that we’re expanding the early access program (EAP) for App Editions to more partners. Our goal this time is to engage additional partners who have previously expressed interest and those who have recently shown enthusiasm for developing editions.

This approach will ensure readiness when we activate the customer General Availability (GA) switch, also known as Milestone 3, in Q2 of calendar year 2025. We have a quick but involved path from EAP to General Availability and are looking for our early adopters to work with us along the way.

Learn more about the EAP participation criteria and requirements here. If you’re interested in participating in the early access program Round 2, please complete the attached form by Mar 3, 2025.

Fixed New Billing System Field and Dual Licensing Reason Code updates in Licenses and Transaction Report

Starting Feb 18, 2025 , we are introducing two updates:

  1. New Billing System Field (newBillingSystem) in Marketplace reporting Licensing API

    • This field indicates whether a customer entitlement is on the new or old billing system.

    • Yes = Entitlement is on the new billing system

    • No = Entitlement is still on the old billing system

    • If case of free apps data this fields  is not available

    • This is particularly important for Marketplace partners participating in App Editions, as it helps identify which cloud customers are on the new vs. old billing system.

    • The field will be maintained when a customer transitions between billing systems.

  2. Dual Licensing Discount Reason Code in Marketplace reporting Transactions API
    We have backfilled data for 62,000 transactions across various partner accounts to correctly display dual licensing discounts for records that were not displaying it earlier. These records were originally not displayed as DUAL_LICENSING but are now correctly labeled. To improve accuracy, we have enhanced our pipeline to map a specific internal reason code(which previously was a free text field) to dual licensing.

    Partners can access these discounts via the Transactions API and read the following fields:

    • Discount Type: Manual

    • Reason Code: DUAL_LICENSING

13 February 2025

Announcement Set Pricing Blocked for 3 Days (February 17th to 19th, 2025)

Multi-instance licensing will soon be available. This licensing model will enable Cloud Enterprise customers to be charged based on the number of unique users of the app across multiple instances, regardless of the number of product instances. We are aiming for Customer GA in May 2025. However, the capability to set multi-instance pricing for apps will be available on Feb 20, 2025.

Important Notice: Pricing Updates Blocked for 3 Days for all apps (February 17th-19th, 2025)

To facilitate a seamless rollout of multi-instance licensing (MIL), we will block set pricing updates for three days (February 17th to 19th, 2025) prior to the multi-instance partner release on Feb 20, 2025. This pause will allow us to run migration and validate APIs effectively.

More details

Important: During the three-day 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.

Rate this page: