Changelog

This is a reminder about the changelog notice issued on October 24, 2024, concerning the deprecation of legacy REST APIs.

The deprecation of Marketplace V1 REST APIs will take effect on January 10, 2025 (Friday). These APIs are intended for Atlassian usage and will not be supported after this date.

Please review your current implementations and make any necessary adjustments before January 10, 2025, to ensure continued functionality.

See the More details section for the APIs list.

From Jan 6, 2025, the use of web triggers will exclude apps from the Runs on Atlassian eligibility criteria.

This is because Forge web triggers currently allow for the egress of customer data returned in response to third-party requests.

While we understand that using web triggers is unavoidable for some use cases involving external systems, we’re also looking to uphold the integrity of the Runs on Atlassian badge for customers.

Atlassian Marketplace APIs will now share data for lifetime free licenses data to our partners through the licenses report.

This license data for life time free apps is based on analytics data generated during the installations of these apps and has been transformed into free licenses. These licenses will only be available via the APIs and not through the user interface on the Marketplace portal.

Partners will be able to access this data via the existing license report APIs (GET as well as EXPORT) using the new showLifeTimeFreeLicenses filter:

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

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

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

More details section contains the applicable fields from licenses report for these new free licenses.

Partners can start accessing this data from Jan 6, 2025. We highly recommend all partners to take a look at the quick reference guide to understand more about this data.

Confluence cloud apps on Atlassian Marketplace now offer up to 150k user tier pricing in line with Confluence cloud. The following new tiers are now available:

• 50,001-60,000

• 60,001-70,000

• 70,001-80,000

• 80,001-90,000

• 90,001-100,000

• 100,001-110,000

• 110,001-120,000

• 120,001-130,000

• 130,001-140,000

• 140,001-150,000

Owing to the upcoming holiday season and partner requests, we are providing a final extension for existing apps with unresolved naming violations, relaxing the hard block for Marketplace apps until January 31, 2025.

Partners with open tickets related to app name violations must address these issues by the new deadline. Failure to do so will render their app names non-compliant with Atlassian's brand guidelines. We have been sending reminders and will continue to provide updates and support to help you transition smoothly before the deadline.

Key Updates and Timelines:

• Hard Block for Current Apps with Violations:

  • A hard block for existing app names with violations will take effect on January 31, 2025. All apps must be updated to comply with the guidelines before this date.

• Soft Block for Existing Apps:

  • As of October 29, 2024, a soft block has been in place for existing apps with naming violations. Partners receive warnings during app version or name updates, but updates are not currently blocked.

• Hard Block for New Apps:

  • Effective October 29, 2024, all new apps must comply with updated branding guidelines. Non-compliant app names will not be accepted for approval submissions.

We appreciate your cooperation as we work together to maintain a consistent and fair Marketplace.

We’re introducing a new program Runs on Atlassian as a Preview on Forge.

The program helps customers identify Forge apps that have no data egress and use data residency-enabled storage on the Atlassian Marketplace via a Runs on Atlassian badge.

To know more about the Runs on Atlassian program, visit https://go.atlassian.com/runs-on-atlassian.
To check if your app is eligible for Runs on Atlassian, go to the Forge CLI documentation.

To ensure compliance with Atlassian's branding guidelines, we are rolling out a hard block starting December 31, 2024, for existing apps with unresolved naming violations. Learn more here. Partners with open tickets related to app name violations must address these issues by this date. Failure to do so will render their app names non-compliant under Atlassian's brand guidelines. We have been sending reminders and will continue to provide updates and support to help you transition smoothly before the deadline.
Key Updates and Timelines:

• Hard Block for Current Apps with Violations:

  • A hard block for existing app names with violations will take effect on December 31, 2024. All apps must be updated to comply with the guidelines before this date.

• Soft Block for Existing Apps:

  • As of October 29, 2024, a soft block has been in place for existing apps with naming violations. Partners receive warnings during app version or name updates, but updates are not currently blocked.

• Hard Block for New Apps:

  • Effective October 29, 2024, all new apps must comply with updated branding guidelines. Non-compliant app names are not accepted for approval submissions.

We appreciate your cooperation as we work together to maintain a consistent and fair Marketplace.

We have identified an issue within our system where the "evaluationOpportunitySize" field in the licenses API displayed ‘NA’ value for approximately 230,000 entitlements on evaluations spread across Server and Data Center hosting type.

This issue was attributed to an incorrect mapping of Marketplace apps to the Atlassian parent product family name.

The issue has now been resolved and Marketplace partners will be able to fetch accurate evaluation opportunity count from licenses API, effective Dec 4, 2024

An issue in our upstream service impacted discount data, leading to missing values in the purchaseDetails.discounts array field of the transaction API for approximately 35,000 transactions, primarily affecting refund transactions.

This issue has now been resolved. Partners will have access to accurately backfilled refund amounts for all relevant transactions starting from Nov 28, 2024.

Marketplace has implemented a minor adjustment to the filtering logic within the license report. Community licenses will now be included in the paid license filter in the license reporting user interface.

Community licenses are subscription-based licenses offered at a 75% discount off the list price. Currently, these licenses can be filtered out using the free filter in the license reporting user interface (UI). Since customers do pay a portion of the subscription and these licenses are classified as paid, we are transitioning these licenses to be included under the paid filter in the licensing UI.

Partners can access their license report to explore this enhancement. We will continue to refine our filters in the future.

As communicated earlier and as a part of our overarching strategy to enhance our core foundations, we are in the process of upgrading our tech stack. With that, we are implementing minor experience enhancements to the Downloads and Versions tab on the Marketplace partner portal:

• Implementing the "Atlassian Design System" to ensure consistency and coherence across all Marketplace interfaces.

• Introducing accessible charts featuring new colors and patterns to improve the readability of the chart on Downloads tab.

• Improving the readability and usability of version listing by enabling a focus on hosting while viewing the released versions on Versions tab.

The enhanced experience will be introduced gradually, starting Nov 25, 2024. Initially, a small percentage of partners will have access, with a phased expansion to all partners over the following week. The objective is to complete the rollout to all our partners by Dec 4, 2024.

For more details, you can refer the quick reference guide.

We now accept bug and incident reports under a single new request type: Ecosystem Support Request. This change simplifies the process of reporting issues to our support team, so that we can handle your issue more efficiently, and ensure consistent handling for all critical issues, particularly incidents.

We’ve also detailed the scope of our Developer and Marketplace support, so you have a better understanding of supported issues and response times.

Marketplace is introducing a logic in the license report for partners to improve the quality of the data we provide. Licenses that do not possess a valid cloud ID, are inactive and do not have a valid transaction will be excluded from the license report.

Licenses enter this state in a specific edge case related to app provisioning. If our system encounters a failure during the app provisioning process (after creating an entitlement). We deactivate the license later, but that can take up to 7 days. During this time, there may be instances where the license appears in the report without a corresponding cloud ID, and lacks a valid transaction. Moving forward, after approximately 7 days, these types of licenses will no longer appear in the license report. While the likelihood of this occurring is minimal, some edge cases/system errors can still cause these.

Please note, we will not perform a historical update to the data. Partners will still be able to view historical licenses that do not have a valid cloud ID and may be active or inactive with or without historical transactions.

As part of a larger Marketplace Technical foundations initiative to improve feature delivery rate, performance and reliability of Marketplace, we’re deprecating more legacy REST APIs. Please read further to understand the changes.

1. Marketplace V1 REST APIs changes:

Last month on 24th October, 2024, we announced the deprecation the V1 APIs intended for use by the marketplace partners. We are now announcing deprecation the remaining V1 APIs, which are intended to be used by Atlassian applications. These will be removed after a period of approximately 2 months from now on 10th January, 2025(Friday) along with the rest of the V1 APIs. Please see the More Details section for the APIs list.

1. Marketplace V2 REST APIs changes:

We’re also announcing here the deprecation of V2 APIs that are intended for use through the Atlassian applications only. Please see the More Details section for the APIs list. These will be removed after a period of approximately 6 months from now at the end of May, 2025.

p.s. As stated, all of these APIs are intended for Atlassian usage and therefore will not be supported in the future and will be deprecated.

We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com