Changelog

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

Marketplace has revised the approach for displaying licensing details related to inactive licenses. Moving forward, our licenses report will consistently present the most up-to-date information regarding these inactive licenses.

We recently noticed that inactive licenses were not consistently displaying the most up-to-date information. Marketplace aggregates reporting data from various internal systems which requires us to navigate different types of delays from these systems to ensure that we deliver accurate reporting data to our partners. An edge case involving lag has resulted in inactive licenses not being consistently updated with the latest period information. This issue has now been resolved.

As a result of this resolution, partners might see updated to some of the fields for some of their licenses:

• maintenanceStartDate - Will point to the latest maintenance start date

• maintenanceEndDate - Will point to the latest maintenance start date

• status - May move from cancelled to inactive

• licenseType - May move from evaluation to commercial etc.

• lastUpdated - To help partners identify which records are affected

Currently, our licenses report does not include evaluation details for $0 licenses. We have now enabled this functionality, allowing the relevant evaluation details fields to be populated for these licenses. Additionally, we are updating the historical data to reflect this change for both active and inactive licenses.

Partners might see some of their licenses getting updated because of this, particularly the following fields in the licenses report:

• evaluationOpportunitySize

• evaluationLicense

• daysToConvertEval

• evaluationStartDate

• evaluationEndDate

• evaluationSaleDate

Starting Oct 29, 2024, based on the announcements on this partner portal page:
Upcoming Branding & Naming Validations for the Atlassian Marketplace - Quick Reference Guide  and the updated App Name branding guidelines: Atlassian brand guidelines for Marketplace Partners , a few updates will take effect:

• For any new public app, we will begin validating app names to ensure compliance with the branding guidelines. Partners will not be able to submit apps for approval if they do not meet these guidelines, effective immediately. Errors will be displayed on the screen.

• For existing apps(apps that are already public version before Oct 22, 2024 ), a hard block will be instituted around Dec 31, 2024. At this point, ECOHELP tickets have been raised for partners to address branding issues in their app names. Additionally, warnings/errors will now appear next to your app names, allowing you to view any validation errors directly. Please watch out for more updates on Upcoming Branding & Naming Validations for the Atlassian Marketplace - Quick Reference Guide page.

We are deprecating Marketplace V1 REST APIs and these will be removed after a period of 2 months from now on 10th January, 2025(Friday). We released V2 REST APIs back in May, 2016 and since then, V1 APIs have been unsupported. We’re cleaning up outdated APIs as part of a larger Marketplace Technical foundations initiative to improve feature delivery rate, performance and reliability of Marketplace for our partners. We are deprecating V1 APIs because they are less reliable, outdated, and have not been maintained since 2016.

According to usage data, almost all of Marketplace Partners are already using V2 APIs already - so it should be no change for them. If you are still using V1 APIs in certain cases, please switch to the V2 alternatives listed in the More Details section by January 10th, 2025.

We are excited to announce the general availability of the enhancements to downloads that we had previously announced.

What are the improvements that we have done?

To recap, we have made improvements to the way we provide and reliability of downloads data:

• We have improved the accuracy of our data by shifting from real-time count updates, which led to discrepancies, to a more reliable asynchronous method of aggregating the count over a full day

• We have improved our monitoring and ability to correct failures promptly, thereby enhancing reliability of this data

Along with improvements:

• To partners, download counts will now be shown on a weekly basis i.e. partners will be able to get this data till the last completed week through the download analytics UI and API

• To customers, on surfaces such as app listing, download counts will be shown till the previous day

• This data will now be served via the existing partner metrics API

Partners can access these changes for downloads from Oct 22, 2024. To learn more about these enhancements, please refer to the quick reference guide.