This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.
To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.
The Forge CLI now supports specifying a limit when starting a bulk-upgrade workflow.
1
forge bulk-upgrade start --limit 100This limit can also specified in non-interactive mode.
1
forge bulk-upgrade start --non-interactive --from-version 2 --to-version 3 --limit 100If the limit parameter is not specified, the CLI will prompt you for a limit as part of its interactive flow.
The Forge CLI will also now indicate when the number of eligible installations exceeds the number that can be performed in a single workflow.
Forge LLMs will move from EAP to Preview on Jun 1, 2026, making it available to all Forge developers as a billable capability.
To ensure a clean cutover, EAP access will be disabled on May 29, 2026 at 00:00 UTC. From Jun 1, 2026 , all Forge LLM usage will be billed.
We are also deprecating the following older model versions, which will not be included in Preview:
claude-sonnet-4-20250514
claude-opus-4-1-20250805
claude-opus-4-5-20251101
What you need to do
• Review the Forge LLMs pricing to understand how credits and billing work.
• Ensure your apps are added to a developer space with active billing details to continue using Forge LLMs on June 1st.
For more information, see the Forge LLMs reference documentation.
We've introduced the Tile component for Forge UI Kit apps, now available in Preview. The Tile component is a rounded square container for displaying assets like emojis, or objects in a consistent, styled way.
The component supports various sizes (from 16px to 48px), customizable background colors using design tokens, optional borders, and adjustable internal padding for different asset types including third-party logos.
For implementation details and examples, see the Tile component documentation.
The Forge CLI downloads app templates from a CDN when running forge create. As part of our ongoing security and reliability improvements, this CDN URL is being deprecated and replaced with a new one.
What's changing:
Old URL (deprecated): https://forge-templates.us-west-2.prod.public.atl-paas.net/
New URL: https://forge-templates-bifrost.prod-east.frontend.public.atl-paas.net/assets/
When:
Effective from @forge/cli@12.20.1: the CLI fetches templates from the new URL.
End of support for old URL: 2026-11-26 (6-month deprecation period, per the Forge deprecation policy).
Who is affected:
Developers running Forge CLI versions older than 12.20.1 that reference the legacy templates URL.
Enterprise environments with firewall allow-lists that include the old CDN domain.
Action required:
Update your Forge CLI to @forge/cli@12.20.1 or later: npm install -g @forge/cli@latest
If you maintain a corporate firewall allow-list, add forge-templates-bifrost.prod-east.frontend.public.atl-paas.net to your permitted domains. You can safely remove forge-templates.us-west-2.prod.public.atl-paas.net after 2026-11-26. Refer to Use the Forge CLI on a corporate network for the full list of required outbound connections.
No changes to app code or manifests are required.
More details: Use the Forge CLI on a corporate network
New UI Kit components for managing file upload are now in preview:
File picker: allows the user to select files stored locally.
File card: displays information about a file (including name, type, and size); this can be used to managed selected files and displaying upload progress.
See how to implement these in our example app.
A new RFC is ready for review at RFC-136
We're introducing three new APIs that let org admins programmatically manage approved-domain app access settings: App access settings.
These APIs complement the existing read-only endpoints in the same group, closing the gap for customers who manage many orgs or want to script onboarding/offboarding flows that previously required the Admin Hub UI.
POST /admin/v2/orgs/{orgId}/app-access-settings/domains — Register a new approved domain for the org, optionally with an initial set of product configurations.
PUT /admin/v2/orgs/{orgId}/app-access-settings/domains/{domain} — Replace the per-product configuration on an existing domain (full replace; products not in the request body are removed).
POST /admin/v2/orgs/{orgId}/app-access-settings/domains/{domain}/products — Add or update a single product configuration on a domain, leaving any other products on that domain untouched.
All three endpoints accept and return the same AppAccessSettingsDomainDetail shape used by the existing GETs.
Same as the existing GETs: OAuth scopes manage:org-data:atlassian-admin (or equivalent admin scope), or Atlassian API tokens with the org-admin role.
Shared per-org budget with the existing GETs.
Fully additive. No existing endpoints, fields, or behaviours are changed.
Previously, we announced an upcoming fix to how Forge SQL returns DATETIME column values when the time component is 00:00:00. We are now rolling out this update on Jun 5, 2026 instead of Oct 6, 2026
As this change relates to a bugfix in an underlying library dependency, deferring the update could expose the platform to security vulnerabilities. However, updating the library as scheduled means rolling out the DATETIME fix earlier than expected.
What's changing:
Previously, querying the value of a DATETIME column where the time component is set to 00:00:00 would result in only the date portion being returned. For example, the value '1970-01-01 00:00:00' would be returned as '1970-01-01'. After this update, the full value including the time component will be correctly returned ('1970-01-01 00:00:00').
This affects DATETIME column values that were set in the following ways:
The value was explicitly set with a time component of 00:00:00, or
The value was set with only the date component, in which case the time component defaults to 00:00:00.
What you should do:
If your Forge app reads DATETIME values from Forge SQL and parses the returned string, verify that your parsing logic handles the full YYYY-MM-DD HH:MM:SS format.
Why we're accelerating this:
Remaining on an outdated version of this library dependency has the potential to leave Forge SQL exposed to security vulnerabilities. We cannot responsibly defer a necessary security update to honour the original grace period. We apologise for the shortened notice and appreciate your understanding.
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:
| Status | License Type |
|---|---|---|
Before introducing the state |
| / |
Interim period |
| |
As of May 20, 2026and onwards |
|
Licenses API
Field - licenseType
Query Parameter - licenseType: legacy_free
/vendors/{vendorId}/reporting/licenses https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-get
/vendors/{vendorId}/reporting/licenses/export https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-licenses-export-get
/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
/vendors/{vendorId}/reporting/sales/transactions https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-reporting/#api-vendors-vendorid-reporting-sales-transactions-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
/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:
Old scale (1–4) | New scale (1–5) |
|---|---|
1 star | 1.25 stars |
2 stars | 2.5 stars |
3 stars | 3.75 stars |
4 stars | 5 stars |
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:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
{
"productId": "acd011b1-1111-45bc-902a-247046a11111",
"reviews": [
{
"id": "fac62ba6-a41d-4ff2-91fc-eec51a1109ijn",
"content": "Great app! Very helpful for our team.",
"responseContent": "Thank you for the feedback!",
"stars": 4,
"date": "2025-01-15T10:30:00Z",
"totalVotes": 8,
"helpfulVotes": 6,
"productHosting": "cloud",
"isFlagged": false,
"authorName": "Jane Smith",
"transitionedToFiveStarRating": false
},
{
"id": "86551fe0-5f38-43f4-iok92-7ef753efbf16",
"content": "Good functionality but could use better documentation.",
"responseContent": "",
"stars": 4,
"date": "2025-01-10T14:22:00Z",
"totalVotes": 3,
"helpfulVotes": 2,
"productHosting": "server",
"isFlagged": false,
"authorName": "Bob Johnson",
"transitionedToFiveStarRating": true
}
],
"cursor": "eyJkYXRlIjoiMjAyNS0wMS0xMCIsImlkIjoiMTIzNDUifQ==",
"count": 2,
"averageStars": 4
}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:
Update integrations to expect stars and averageStars on a 1–5 scale.
Incorporate the transitionedToFiveStarRating flag if your systems distinguish between legacy and new reviews.
For more details, see the Quick Reference Guide.
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.
Suppressing events means no issue updated events will be emitted - not only for your app, but for all apps installed in the Jira instance.
Other apps may retain stale data for the updated field, which can lead to inconsistent or confusing behavior.
Marketplace apps should avoid using this parameter, as it may cause incompatibilities with other apps that depend on up-to-date issue data.
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
Rate this page: