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.
We are adjusting how some JQL features behave to keep search fast and reliable. Queries using functions membersof() and aqlFunction() that expand to very large sets will return an error identifying the clause to adjust. For comments, worklogs, and issue history (searches using operators WAS or CHANGED), JQL searches cover only the most recent entries per issue.
Jira data and permissions are unchanged.
Effective date: Aug 18, 2026
This update affects search behavior only. Group- and asset-based functions that fetch over 10,000 items will not run. Time-ordered content (comments, worklogs, history) remains available in Jira without any changes, but JQL operates on the most recent 1,000 items per issue. The table below lists the thresholds, what occurs, and how to adjust queries.
Function / clause | Threshold | What happens | How to mitigate |
|---|---|---|---|
| 10,000 matched assets per function | Query returns a clear error | Refine AQL/IQL; add selective criteria; split broad schemes. |
| 10,000 resolved users per function | Query returns a clear error | Use smaller groups; split umbrella groups; |
| 10,000 resolved users per function | Query returns a clear error | Reduce org size in queries; prefer labels/custom fields. |
Issue history (JQL using operators | 10,000 searchable changes per issue | Search covers the most recent changes only. | Rely on recent activity; use issue view/exports for older changes. |
Comments | 1,000 searchable comments per issue | Search covers the most recent comments only. | Rely on recent activity; use issue view/exports for older changes. |
Worklogs | 1,000 searchable worklogs per issue | Search covers the most recent worklogs only. | Rely on recent activity; use issue view/exports for older changes. |
Text field | First 50 characters used | Sorting uses only the first 50 characters. | Add sorting by updated/created or other fields. |
We are introducing rate limits for Forge Realtime to ensure the stability and reliability of the service for all apps.
What’s changing
Starting June 26, 2026, a rate limit of 50 requests per app installation per second will be enforced for Forge Realtime. For more information, see our rate limit documentation.
Based on our current telemetry, no existing Forge apps exceed this limit, so we do not expect any immediate impact on your app's performance. This change is a proactive measure to maintain service health.
What you need to do
Review your app's use of the Realtime Events API and Bridge API Realtime method to ensure your request frequency remains within the new limit.
If you anticipate needing a higher rate limit for a specific use case, please reach out via the developer support portal.
As Connect approaches end of support in December 2026, we are starting to roll out customer messaging in the admin experience to inform admins when an installed app runs on a soon to be unsupported platform, Connect. Following on from our previous announcement, this messaging will gradually rollout over the next week to be live in production for non-public apps only and is scoped to the admin experience, end users will not see any notices at this stage.
On Jun 2, 2026, we will enable customer messaging on Developer Canary tenants for public apps. This will include notices in admin facing experiences so enrolled partners can preview the exact messaging their customers will see and have the chance to adopt the new connectToForgeMigration module in their manifest before it goes live in production.
If your app has yet to migrate fully to Forge (or has a migration plan), you can adopt the new connectToForgeMigration module in your Forge manifest (docs here). This module lets you provide a URL to your migration guidance, which will be surfaced directly in the messaging customers see, replacing the generic notice with app-specific information.
What you need to do:
If your app is in the Developer Canary Program, expect to see customer messaging on your canary tenants starting Jun 2, 2026.
Adopt the connectToForgeMigration module in your manifest to customise the guidance your customers will eventually see.
Production rollout for public apps is planned to start in July. You will receive at least one week's advance notice before that happens. There will be an extended rollout of this messaging across 3 months. From September onwards, all customers with apps installed that use any Connect modules will see this messaging.
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
The new headingLevel prop for @atlaskit/section-message will allow for a more accessible heading structure when using the title prop. See the W3C headings page for more information on how to nest headings correctly.
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 | INACTIVE | COMMERCIAL / EVALUATION |
Interim period | ACTIVE | FREE |
As of May 20, 2026and onwards | ACTIVE | LEGACY FREE |
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
Rate this page: