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.
The marketplace license report has been enhanced to accurately handle some of the edge cases with respect to license status. Moving forward, instead of the created date of licenses, we will take into account the maintenance start and end dates to display their status in our license report. This will especially help us in handling some of the edge cases such as pre billed licenses.
Partners will now be able to the correct point in time status of licenses in cases when multiple period of the same licenses are bought but at different times.
What are the changes in license report some partners might see:
Due to the presented change in our logic, while most of the data will remain the same, some partners might observe some of the licenses in their reports move from expired to active. These are licenses which have an edge case such as a pre-billed period that was bought before another period of the same license was paid for etc.
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 Installation tab on the Marketplace partner portal:
Ensuring a consistent partner experience, similar to the Reporting changes implemented towards the end of last year (Nov '23).
Data plotted will be improved to reflect a latency reduction from 1 week to 1 day, aligning with the installation counts displayed on the app details page.
Introducing accessible charts featuring new colors and patterns to improve the readability of the chart
The enhanced experience will be introduced gradually, starting Sep 24, 2024. Initially, a small percentage of partners will have access, with a phased expansion to all partners over the following week. The roll out will be completed for all our partners by Oct 4, 2024
For more details, you can refer the quick reference guide.
We are improving the logic behind the Evaluations report for cloud apps offered on the Marketplace.
For Server and DC, a distinct evaluation license is generated, and the Evaluations report indicates the count of evaluation licenses initiated within a specific date range. Conversely, in the cloud scenario, the license transitions from evaluation to paid status upon a customer purchasing a subscription. Once the cloud license shifts to a paid status, the historical count is reduced in the Evaluations report.
To improve the accuracy of historical cloud evaluation counts, we have revised our approach. We will now consider the evaluation start date of the cloud license to generate a comprehensive Evaluations report. Specifically for cloud licenses, the report will consistently display all licenses initiated for evaluation within a specified date range. This logic will ensure that even historically, the report shows the cloud licenses that were under evaluation even if their status has now changed.
The data generated with the enhanced logic for counting evaluations will be available to all partners from Sep 5, 2024. From then on, the Evaluations report in the Marketplace account and the API will show data according to the new logic.
How can you access it?
API: Evaluations Report
Evaluations report UI: https://marketplace.atlassian.com/manage/vendors/{vendorId}/reporting/evaluations
For more details, you can read the quick reference guide.
As previously mentioned, we are implementing new validation checks during app publish flows and version update flows to ensure compliance with our branding guidelines for app naming and logo usage. In order to further maintain a fair and equitable Marketplace, we have adjusted our original announcement to now include a grandfathering clause and added flexibility to branding guidelines. Learn more here.
In light of these adjustments, we’ve also revised the rollout timelines to give you sufficient time for compliance:
Soft Block for Existing Apps: Starting Oct 15, 2024, a soft block will be applied to existing apps with naming violations. Partners will receive warnings about the underlying violation during app version or name updates, but these updates will not be blocked.
Hard Block for New Apps: From Oct 15, 2024, onward, all new apps must comply with the updated guidelines. Any app names that do not meet the criteria will not be accepted for approval submission.
Hard Block for Current Apps with Violations: The hard block for existing app names with violations has been extended until the end of this year Dec 31, 2024 giving you ample time to make the necessary adjustments.
Atlassian is launching an early access program for app editions on Marketplace, starting in Q4 CY24 to assist early access participants with Cloud paid via Atlassian apps to build app editions and encourage customer upgrades.
The documentation for this EAP is available at https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/531104323/App+Editions+Resource+Hub.
In our previous correspondence, we discussed the planned deprecation of Sync APIs for exporting licenses and transaction data with the introduction of the new Async APIs. Upon usage analysis, it has come to our attention that many partners still heavily depend on Sync APIs.
Therefore, we have opted to maintain support for Sync APIs, allowing you to utilize them as usual. Nevertheless, adjustments will be made to the data provided by Sync APIs. Specifically, the data range accessible through Sync APIs will be restricted to a few years instead of offering lifetime or extensive historical data. The exact details will be communicated before implementation. Until then, there is no change to the usage of Sync APIs.
This adjustment enables the use of Sync APIs for smaller, more recent data inquiries, while larger datasets, such as lifetime or extensive historical data, will necessitate the use of Async APIs. Details regarding the precise data range limitations for Sync APIs will be communicated once finalized.
App Editions EAP Opportunity
We would like to remind you that App Editions EAP applications are due today i.e. Friday, August 23rd! This EAP will give you the opportunity to share your feedback and insights on your experience and collaborate closely with the Marketplace team to build the advanced edition of your app.We are looking forward to working with you on this exciting initiative.
We’ve launched an early access program (EAP) (EAP form here) for app editions on the Atlassian Marketplace! If you're interested in participating in the early access program, please review the EAP expectations and details here and fill out the attached interest form by Aug 16, 2024.
Why join the EAP?
We have a quick but involved path from EAP to General Availability and are looking for partners to join us on this journey. During the early access phase, participants will work closely with the Marketplace teams to build, test, publish, and promote new app editions. This collaboration ensures a smooth transition to the advanced edition and a successful launch.
EAP timeline:
Start Date: End of August 2024
End Date: December 2024
We look forward to partnering with you!
We're excited to announce the launch of the early access program (EAP) (EAP form here) for app editions on the Atlassian Marketplace!
Why join the EAP?
We have a quick but involved path from EAP to General Availability and are looking for partners to join us on this journey. During the early access phase, participants will work closely with the Marketplace teams to build, test, publish, and promote new app editions. This collaboration ensures a smooth transition to the advanced edition and a successful launch.
EAP timeline:
Start Date: End of August 2024
End Date: December 2024
How to sign up?
If you're interested in participating in the early access program, please fill out the attached interest form by Aug 16, 2024. Also, please review the EAP expectations and details here. We look forward to working with you!
Rollout: Progressive rollout for users. in progress
Starting Aug 5, 2024, the Marketplace REST APIs, specifically within the /rest/2/addons endpoint, will experience some latency in reflecting changes to app listings. This is due to the updation of the underlying search infrastructure.
We’ve introduced a new --license option to the forge install command.
This enhancement lets you specify and test different license states for Forge apps in non-production environments, providing greater flexibility and control during the development and testing phases. This essentially means that you no longer have to mock your app code as if it’s in production to test your Forge app in different license states.
The following license values are supported:
active
inactive
trial
See Listing Forge apps and Forge CLI reference documentation for more details.
Here is the recent update on this Changelog.
Following our announcement regarding the introduction of App name validations to Marketplace, we received numerous inquiries from partners seeking additional time and clarification on the validations. In response, we have decided to ease the transition by implementing the following measures:
To enhance partners' comprehension of the app name validations, we are introducing an API endpoint that will allow partners to input an app name and receive a list of errors/warnings associated with that name. Partners can utilize this API endpoint to verify both existing app names and potential new app names they may consider in the future. More details on this API endpoint will be provided in a separate Changelog.
The deadline of Aug 15, 2024 will not act as a strict barrier for existing app names post-validation. We will be converting error messages to warnings for the following 30 days, ensuring that partner have sufficient time to address these violations and enhance the branding of their apps by September 15th, 2024.During this period, partners can view validation errors but will still be able to proceed with App version updates. However, net new apps submitted during this time will face a strict block and must adhere to the validations to progress towards review submission.
In order to enhance visibility and ensure that no apps are overlooked by partners, we will compile a list of apps with corresponding validation failures and generate tickets to notify partners of any branding violations detected and the operations team will reach out to you.
We are pleased to inform all Atlassian Marketplace partners that the hard-set limit for individual artifacts has been raised to 250 MB from 150 MB. This modification aims to facilitate a better uploading experience and effectively support larger file sizes.
As mentioned on our Previous Changelog - https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-1371, we are thrilled to share additional information regarding the new replacement APIs.
The DAC documentation for the new APIs has been released. Below is the list of replacement APIs available to our partners. These APIs are designed to unify access control management for team members across the Marketplace and Developer Console in the future. Please review the DAC documentation links to gain a deeper understanding.
Currently, these APIs only cater to deployment and are in development. You can expect some minor changes in the coming months. They are expected to be available for partners to use by October 2024.
Marketplace team has made a few updates to the licenses and transactions reporting APIs in terms of additional fields and filters.
Filter for manual invoices: During specific scenarios such as apps for enterprise parent licenses, invoices are manually generated. These invoices are then incorporated into the transactions report. To aid partners in effortlessly identifying and filtering out manually created invoices from their transaction history, we are introducing a new query parameter.
includeManualInvoice can be passed as a parameter while requesting for transactions with possible values as true or false. By default, the value will be set as false if not specified.
For more on how to use this parameter, partners can read the documentation here
Field for differentiating Atlassian and Non-Atlassian licenses: The license report from Marketplace includes licenses from various customer types. To assist partners in distinguishing between Atlassian-owned and non Atlassian owned licenses, a new field has been incorporated into the license response.
licenseSourceType in the licenses response will differentiate customers based on their domain and will have values Atlassian and Non-Atlassian
For more on how to use this parameter, partners can read the documentation here
Unique identifier for line items in transactions: The transactions report lacks unique IDs at the line item level, providing only an invoice ID. This limitation complicates the management, tracking, and updating of individual items within an order, particularly when an invoice contains multiple line items from the same application, making it challenging to differentiate between these items. To mitigate this issue, we are introducing a unique identifier for each line item.
transactionLineItemId in the transactions response will provide a unique identifier for each line item in transactions report
For more on how to use this parameter, partners can read the documentation here
Exposure of transaction account ID: In CCP cloud subscriptions, we use a unique identifier for each transaction account within Atlassian’s ecosystem. To help partners track and group licenses belonging to a specific billing entity, our licenses report will now contain this unique identifier in the response.
transactionAccountId is the licenses response will provide the transaction account ID
For more on how to use this parameter, partners can read the documentation here
We recently identified an issue where the evaluationOpportunitySize and tier fields in our license report were inaccurately displaying null or unknown response values. This was due to a reliance on the parent period for retrieving values in these fields. We have successfully addressed this issue and have updated all historical records along with refreshing the lastUpdated field.
Rate this page: