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’re simplifying how fields are associated and configured in Jira by introducing field schemes, a new model that will replace field configurations and field configuration schemes. This change also affects how field contexts will be used for visibility.
Field schemes will become the source of truth of what work types a field can appear on for Spaces.
Field contexts define the default values for fields and the options that are available for users to select. Given contexts will no longer be used to restrict where fields are available, every field will have a global context which is always present and cannot be deleted.
Screens, Screen schemes and Work item layouts determine what users see when they are creating or viewing a work item in the full page view.
This will involve the following changes:
Component | Update | Date |
|---|---|---|
New field associations | Open Beta (sign up here) | February 2026 |
GA | April 2026 | |
(see More details for complete list of APIs) | July 2026 | |
All unused fields from schemes | (to improve Jira’s performance) | July 2026 |
For more context, please review the announcement blog post and related RFCs.
To determine or manage a fields availability we recommend using APIs that support both field configurations and the future field schemes, namely:
Field schemes (see RFC-105)
The following API changes will be implemented on Feb 2026 for beta customers, April 2026 for GA:
Delete custom field context: will no longer support removing global contexts.
Add issue types to context: will no longer support restricting the global context to certain issue types.
Assign custom field context to projects: will no longer support restricting the global context to certain projects.
Create project: changes to template format (see RFC-121).
All Field configuration APIs will be removed on July 2026:
We are extending the deprecation period of the Convert content body v1 REST API in Confluence Cloud to Aug 5, 2026 .
This API was originally scheduled for removal on Feb 1, 2026. We also advised that affected developers use the Asynchronously convert content body endpoint instead. However, we’ve discovered some issues that may prevent them from doing so (please refer to CONFCLOUD-82501 for details and updates on this).
We expect to have all related issues addressed before this new deprecation period ends.
Forge customer-managed egress and remotes are now available through Forge’s Early Access Program (EAP). This capability lets admins control which external domains and remotes a Forge app can connect to, and configure those connections per installation. This approach is useful for apps that need to load data from customer-defined URLs, without declaring every possible destination up front in the manifest.
To join the EAP, complete this sign-up form.
We've added new methods to the webTrigger API from @forge/api that allow you to query and delete previously created web trigger URLs.
webTrigger.queryUrls() — Retrieve all web trigger URLs for your app, optionally filtered by module key
webTrigger.deleteUrl() — Delete a specific web trigger URL
For implementation details and examples, see the Web trigger runtime API documentation.
The Forge migration timeout logic for now uses a 15-minute sliding window from the last event status change (instead of 15 minutes from when the event was created). See https://developer.atlassian.com/platform/app-migration/report-progress-for-forge/ for more information.
Support for dynamically retrieving the list of supported models is now available in Forge LLMs. The new list function in the @forge/llm SDK lets apps fetch the latest list of models, returning a response like:
1
2
3
4
5
6
7
8
9
10
11
12
{
"models": [
{
"model": "claude-sonnet-4-20250514",
"status": "active"
},
{
"model": "claude-opus-4-20250514",
"status": "deprecated"
}
]
}You can filter on the status field to ensure your app always uses an active model and avoid breaking changes when a model is removed.
Forge LLMs remain in Early Access (EAP). Due to high demand, participation is limited. To request access, join the waitlist here.
For implementation details, refer to the documentation here.
You can now migrate a Connect Jira Issue Field module to Forge's custom field module. The functionality is now available for String, Number and Read-only fields.
See https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields/ for more details.
Forge app REST APIs let your app expose its own HTTP endpoints so that external systems can call your app code running on Forge.
These Forge app REST APIs are secured with developer-defined scopes and use 3LO (OAuth 2.0) for authentication and authorization. You define the endpoints in your app manifest using the apiRoute module.
This capability is currently in Preview and is available for Jira and Confluence Forge apps. This is currently not available in Isolated Cloud.
To learn how to expose REST APIs in your Forge app, see Expose Forge app REST APIs. For a step-by-step tutorial on configuring a 3LO integration to access exposed REST APIs, see Access REST APIs exposed by a Forge app.
Forge embedded macros are now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
Forge bodied macro apps can now render embedded Forge macro apps through the AdfRenderer component (UI Kit) and the view.createAdfRendererIframeProps method from @forge/bridge (Custom UI).
For more information, see the updated documentation for Forge rich-text bodied macros.
A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-125-ui-modification-for-forge-custom-fields/98439
As previously mentioned in CHANGE-2770, support for several cross-workspace APIs has ended.
We are announcing the availability of two new public REST APIs that return information about the accessible workspaces for a user:
These new endpoints can be used alongside existing single-workspace scoped APIs to serve as replacements for the deprecated APIs.
Below is a table summarizing the deprecated APIs and the corresponding alternative APIs that we suggest transitioning to.
| Deprecated API description | Deprecated endpoint and link | Suggested alternative APIs |
1 | Returns a paginated list of all public repositories. |
|
|
2 | Returns an object for each repository the caller has explicit access to and their effective permission. |
|
|
3 | Returns all snippets. |
|
|
4 | Returns an object for each workspace the caller is a member of, and their effective role. |
|
|
5 | Returns a list of workspaces accessible by the authenticated user. |
|
For the first three deprecated APIs, if you already have a single workspace, simply transition to the workspace-scoped alternative by including the workspace slug or UUID in the request path.
However, if you do not already have a single workspace, we suggest using the workspace‑scoped APIs in combination with the new /2.0/user/workspaces API.
Use the /2.0/user/workspaces to get all accessible workspaces for the user
Request to workspace‑scoped alternative endpoint (example: /2.0/repositories/{workspace})
Option 1: select one accessible workspace to use in a request to the scoped endpoint (1 request)
Option 2: make a request for each accessible workspace and aggregate the results (N requests)
A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-124-evolving-the-marketplace-trust-program/98418
We are extending the deprecation window for the following internal API that we previously announced would be removed from Confluence Cloud.
/download/attachments/{id}/{id}
This endpoint is still available via API token access in Confluence Cloud, and will remain available for 3 months from today until Apr 14, 2026, when we will remove API token access and such requests fail. All other endpoints from the announcement are still removed as stated.
Key Dates:
Deprecation announcement: Jan 15, 2026
Removal date: Apr 14, 2026
Why is this happening?
This API is not intended public use and is not supported.
What will happen?
On and after the removal date, all API token access requests to the listed endpoints will fail.
Action Required
Before the removal date, we recommend migrating to the Get URI to download attachment endpoint as an alternative.
Jira global background scripts are now available in Preview. This feature enables you to add an invisible container that coordinates data and behavior across all pages in Jira, enabling advanced integrations and automations.
We’re releasing this feature in preview to gather feedback and help you prepare for upcoming changes. You can use global background scripts in production environments during the preview period.
For more information, see Jira global background scripts (Preview)
As announced in July 2025, a number of glyphs for the Icon component will now be removed.
Rate this page: