Atlassian developer changelog

What’s changing

We’ve introduced a new paginated endpoint to retrieve uploaded file metadata. This change helps reduce memory usage when handling large amounts of data during migrations.

• Forge remote apps can now use the new endpoint: /app/migration/forge/v1/data/{transferId}/page.

• Forge functions can now use the migration.getAppDataIterator method, available in @forge/api version 7.2.0 or greater.

We will announce the deprecation of the /all endpoint at a later date.

What you need to do

If your app handles large volumes of migration data, we recommend updating your implementation to use the new paginated methods:

• For Forge remote apps: Update your requests to use the new paginated endpoint.

• For Forge functions: Ensure you are using @forge/api version 7.2.0 or higher and migrate to migration.getAppDataIterator.

In reference to https://developer.atlassian.com/platform/forge/changelog/#CHANGE-2876, we introduced a new state—Legacy free licensing—for:

Apps past their subscription or trial end have moved to a legacy “free” licensing state. These inactive installations remain unaffected by the new uninstall flow until an admin initiates uninstall.

For a time, these licenses appeared as FREE ACTIVE licenses on the Marketplace Reporting portal and API responses. (See https://jira.atlassian.com/browse/MP-556 )

We are adding a new license type, Legacy Free to signify those licenses, to API endpoints and the Reporting UI. It will be available from May 20, 2026.

For example, when viewing a specific app’s license:

• Licenses API

  • Field - licenseType

  • Query Parameter - licenseType: legacy_free

  • GET /vendors/{vendorId}/reporting/licenses https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-get

  • GET /vendors/{vendorId}/reporting/licenses/export https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-export-get

  • POST /vendors/{vendorId}/reporting/licenses/async/exporthttps://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-async-export-post

• Transactions API

  • Field - purchaseDetails.licenseType

  • GET /vendors/{vendorId}/reporting/sales/transactions https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-get

  • GET /vendors/{vendorId}/reporting/sales/transactions/exporthttps://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-export-get

  • POST /vendors/{vendorId}/reporting/sales/transactions/async/exporthttps://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-async-export-post

• Licenses in Marketplace Reporting Portal

  • Filter - License Type: Legacy Free

  • License Type will be shown as Legacy Free

  •  

     

We are transitioning the Atlassian Marketplace rating scale from 1–4 stars to 1–5 stars. This change applies to all listed Marketplace apps — free and paid — across the Marketplace website and embedded experiences in Jira and Confluence.

Moving to a 5-star scale aligns the Atlassian Marketplace with industry-standard rating systems, giving customers a more intuitive, granular way to evaluate and compare apps.

What’s changing

• Your app’s overall aggregate rating will now be displayed on a 5-star scale.

• A linear conversion maps existing ratings to the new scale:

• Historical reviews will keep their original star ratings on the reviews tab. For example, a review originally submitted as 3/4 stars remains displayed as 3/4. Only the aggregate app rating is shown on the new 5-star scale.

• New reviews submitted after today’s date May 20, 2026 will use the 5-star scale by default.

• Customers can edit previous reviews. Users who previously rated an app will see a tooltip when editing their review explaining the scale conversion and allowing them to update their rating if they choose. This tooltip only appears when a customer actively edits a review — it won’t surface unprompted.

• Data Center apps: Marketplace web surfaces will display ratings on the 5-star scale for Data Center apps. The Universal Plugin Manager (UPM) within Data Center products will continue to show ratings on the 1–4 scale.

API changes

The averageStars and stars fields in Marketplace public APIs now reflect the 5-star scale. A new boolean field, transitionedToFiveStarRating, has been added to individual review objects to indicate which scale was used.

Affected endpoints:

• rest/2/addons

  rest/2/addons/vendor/{vendorId}

  rest/2/addons/{addonKey}

  • reviews.averageStars → 1–5 scale

• rest/2/addons/{addonKey}/reviews

  rest/2/addons/{addonKey}/reviews/id/{reviewId}

  rest/2/addons/{addonKey}/reviews/mine

  • stars → 1–5 scale

  • transitionedToFiveStarRating → true if the review was submitted on the 5-star scale; false if it originated on the 4-star scale

• rest/3/products/{productId}/reviews

  rest/3/products/{productId}/reviews/{reviewId}

  • Same behavior as above for stars and transitionedToFiveStarRating

Sample API response:

Action required

For most partners, no action is required — Atlassian handles the migration automatically.

However, if you consume rating data via Marketplace APIs, you should:

1. Update integrations to expect stars and averageStars on a 1–5 scale.

2. Incorporate the transitionedToFiveStarRating flag if your systems distinguish between legacy and new reviews.

We’re pleased to announce that Crowd 7.2.0 is now available. We have made some security enhancements and some changes to the supported platform. Explore Crowd 7.2.0 to see the full list of updates.

A new optional boolean parameter, generateAppEvents has been introduced to the following Jira Cloud REST API endpoints

• POST /rest/api/2/app/field/value - Update custom fields

• PUT /rest/api/2/app/field/{fieldIdOrKey}/value - Update custom field value

What it does: When set to false, this parameter suppresses the generation of app events triggered by the update. Specifically, it prevents issue updated events from being dispatched to:

• Forge app event listeners

• Connect app event listeners

• OAuth 2.0 app webhooks

• Admin-configured webhooks (registered via the Jira admin UI)

Default behavior: When omitted or set to true, all app events are generated as usual.

The jira:actionValidator module (Preview) now supports the workItemTypeChanged action across multiple flows, enabling custom validation whenever a user changes a work item's type. The validator is triggered in:

• Issue view - the user changes the work item type from the type field on the issue view.

• Move issue - when the work item type changes as part of moving an issue.

• Bulk move/migrate - the work item type changes as part of a bulk move or migration.

• Convert to subtask - when a standard work item is converted to a subtask type.

• Convert subtask to a work item - when a subtask is converted to a standard work item.

Also, a new context variable newIssueTypeData (type: IssueType) has been onboarded alongside the existing newIssueType (type: String, returns the issue type ID), allowing more refined conditions on the target work item type within your Jira expression.

Read more here - https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-action-validator/#workitemtypechanged

The navigation packages @atlaskit/atlassian-navigation, @atlaskit/page-layout, and @atlaskit/side-navigation are being deprecated in favor of our new navigation system.

What’s changing
Atlassian apps are moving to a new navigation system with an updated visual language. The @atlaskit/navigation-system package delivers this new experience and replaces all three legacy navigation packages.

Existing versions will remain available on npm, but these packages will no longer receive updates, bug fixes, or security patches after the deprecation window closes.

What you need to do
You should migrate your apps to the new navigation system before the deprecation window closes on December 1, 2026. After this date, these packages will no longer be maintained, and teams will be responsible for addressing any issues themselves.

Follow these steps to migrate:

• Review the detailed migration guide for technical instructions.

• Replace legacy package imports with the new @atlaskit/navigation-system components.

• Update your app's layout to align with the new visual language.

Action needed by June 30, 2026: If you have an Atlassian Bug Bounty program, it must be made public to maintain your program status and Marketplace badges.

The good news: you don't need to be fully public by then — you just need to submit an ECOHELP ticket to start the process. Submitting by June 30th protects your program.

Here's what to do:

1. Review the full requirements here

2. Raise an ECOHELP ticket here

Please note:

• Tickets not submitted by June 30th will be automatically closed.

• Submitted tickets that are inactive for 14 days will also be closed.

• Either may result in your program being paused and the removal of associated Marketplace badges.

We’ve added a new field additionalDetails to the response object for the validate update workflows and validate create workflows APIs.

This will contain additional context if applicable related to the validation warnings and errors returned from the APIs.

The Revoke portal-only access for user JSM API is now generally available (GA). We have removed the experimental flag, meaning the API will no longer be modified without prior notice.

What's changing

• GA Status: The API is no longer experimental.

• Error Handling: We've updated the status code from 400 to 404 when a passed accountId does not exist.

What you need to do

If you are currently using this API, update your error handling to account for the new 404 status code when a user is not found. You can find the full technical details in the Jira Service Management Cloud REST API documentation.

We're excited to announce that the downloadable product catalog CSV, available via the Marketplace V3 Product Catalog Snapshot APIs, has been enhanced with Total Install Counts.

This new field provides the aggregate number of installations for each app. For more details see: V3-Product Catalog Snapshot API

A filter to breakdown usage of function compute by compute type (sync or async) is now available in the Forge Developer Console’s Usage and Charges section.

• Sync: Synchronous function executions.

• Async: Asynchronous function executions.

This filter is available on the detailed Usage view of Functions - compute usage and the Site breakdown view.

No action is required. However, we recommend using this filter to understand your asynchronous compute consumption before billing for this compute type begins on July 1, 2026. For more context, see our previous announcement: CHANGE-3120

We’ve added an optional urlFormat field to the webtrigger module in manifest.yml so you can choose which URL format Forge uses for each web trigger. This field accepts two values:

• v1: uses the existing app-based URL format, and remains the default when urlFormat isn’t specified (for backwards compatibility).

• v2: uses a new installation-based URL format with an improved domain and path. Use v2 for new web triggers and when you want to opt in to the newer URL style.

Future web trigger capabilities will require urlFormat: v2, and at that point urlFormat will become a required field.

We've added new components to UI Kit, now available in Preview in the latest version of @forge/react:

• Bleed

• Breadcrumbs

• BreadcrumbsItem

• Pagination

For implementation details and examples, see the documentation links for each component.

Forge custom fields can no longer be edited through the legacy bulk edit wizard (/secure/views/bulkedit/BulkEditDetails.jspa). On the legacy screen, they now appear under Unavailable actions with a redirect message.

Forge custom fields remain fully supported in the new bulk edit experience, available from the list view, backlog view, and JQL search page.