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.
What’s changing
The requestTeamworkGraph() Forge bridge API has moved from the Early Access Program (EAP) to Preview.
You can query Teamwork Graph directly from UI Kit and Custom UI frontends using @forge/bridge, without routing requests through a Forge backend function.
Requests run on behalf of the current user and respect their permissions. Your app must also declare the scopes required by each query.
What you need to do
Update @forge/bridge in your app’s frontend directory:
1
npm install @forge/bridge@latestReview the permissions in your manifest.yml and declare the scopes required for the objects your queries access. See the Teamwork Graph scopes reference.
Use requestTeamworkGraph() to execute queries from your frontend.
For implementation details, see the requestTeamworkGraph reference and Teamwork Graph API guide.
What's changing
You can now customise the background of the platform-managed ADF renderer iframe in Forge Custom UI bodied macros. By using the new background option in view.createAdfRendererIframeProps(), you can ensure your rendered content blends seamlessly with your app's design and the Confluence theme.
Supported values for the background option include transparent, Atlassian Design System background tokens and hex colour codes.
What you need to do
To use this feature, update your @forge/bridge package to the latest version and update your macro's implementation:
Ensure your macro is configured as a bodied macro in manifest.yml with layout: bodied.
Update your call to view.createAdfRendererIframeProps() to include the background property
For more information, see documentation.
Forge Object Store is deprecating the allowed values in the checksumType field in the createUploadUrl and createPublicUploadUrl methods in @forge/object-store package and in GeneratedMetadata as part of objectStore API in the @forge/bridge package . All checksums are now required to use the SHA256 algorithm.
Starting December 10, 2026, any requests using other checksum types (such as SHA1, CRC32, or CRC32C) will be rejected with an HTTP 400 Unsupported Media Type status and the error code CHECKSUM_TYPE_UNSUPPORTED.
We will be releasing a new major version of the @forge/object-store package that removes all other types from the checksumType field except for SHA256.
What you need to do
Update your app code to ensure all objects are hashed using the SHA256 algorithm.
If you are manually passing checksumType to createUploadUrl or createPublicUploadUrl, update the value to 'SHA256'.
Upgrade to the latest major version of @forge/object-store once available to align with the new API signature.
For more details on how to implement SHA256 checksums, refer to the Forge Object Store API documentation.
If your app currently uses a different checksum type and you cannot migrate within the 1-month window, please reach out via an ECOHELP ticket.
The custom field context default value REST APIs deprecation has been extended to July 2027. This extension provides additional time to migrate as we adjust the timelines for supporting multiple default values per context.
Updated deprecation timeline:
November 4 2026: New GET /rest/api/3/field/{fieldId}/context/defaultValues endpoint available for testing.
November-December 2026: Early access begins for multiple default values per context and the new PUT /rest/api/3/field/{fieldId}/context/defaultValues REST API. You can sign up for early access via this form.
January 2027: GA launch of multiple default values per context and the new PUT /rest/api/3/field/{fieldId}/context/defaultValues REST API.
July 2027: The existing (deprecated) default values APIs will be removed.
Summary
Support inline-bodied layouts for Confluence Forge macros
Description
Confluence Forge macros now support layout: inline-bodied for macros with rich-text bodies that should render inline with surrounding text. This layout supports both UI Kit and Custom UI, including macros migrated from Connect.
What you need to do
Use Forge CLI 14.0.0 or later.
Set layout: inline-bodied on the relevant macro module in your manifest.yml.
If you are migrating a Connect macro with bodyType: rich-text and outputType: inline, apply this layout to the corresponding Forge macro.
Layout behavior
Macros appear as blocks while editing, this is the default behavior from Confluence Data Center and the Legacy Editor. Inline presentation in view mode requires a single paragraph of inline-compatible content. Multiple paragraphs or block elements, such as tables, lists, and headings, cause the macro to render as a block.
Export behavior depends on the export context and the content returned by your adfExport function. See the macro reference for supported behavior and requirements.
Documentation
Forge apps can now make online and offline calls on behalf of unverified user accounts using user impersonation including invocations from Forge functions and Forge Remote.
Online calls use the invoking user's context, while offline calls can act on behalf of a specified unverified user asUser(accountId) where supported.
Existing Forge app permissions, product permissions, and API-specific access controls continue to apply. This change does not enable anonymous-user access.
This includes support for unverified external customer accounts in Jira Service Management (such as email-created portal customers with qm: account IDs), as well as unverified Atlassian accounts
Atlassian MCP now supports Claude-issued Managed Auth, enabling Enterprise-managed authentication (EMA) / Cross App Access (XAA) directly from Claude without a dependency on an additional IdP.
For more details on how to get started, please review the Configure enterprise-managed authentication guide.
Bitbucket Data Center and Server 9.4.27 and 10.2.9 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
Following our deprecation notice of the 'draft' parameters on workflow rule APIS on Apr 22, 2026
As of Nov 2, 2026, the ability to filter on and modify draft workflows has been removed from the Workflow transition rules APIs. Calls that include the draft parameter now return an HTTP 400 (Bad Request) response and WorkflowId objects will no longer include the draft attribute.
Forge storage data residency moves no longer cause host product downtime
Until now, moving an app's Forge-hosted storage to another region meant taking its host product offline. That happened even when the host product had already moved.
Now, only the app installation being moved goes offline. The host product, and any other Atlassian product the app is linked to, remains fully available throughout the move.
What's affected while the app installation is offline
Storage, functions, and UI are unavailable: Calls to Forge-hosted storage, backend function invocations, resolver-driven UI, and dynamic component updates are blocked.
Upgrades and uninstalls are paused: Major version upgrades and uninstalls can't run until the move is finished.
Product events are queued, not lost: Atlassian product events sent to the app during the move are held and delivered automatically once the move completes.
This change applies automatically to all apps that use Forge-hosted storage
Forge is enabling user-token support for unlicensed users in Forge function and Forge Remote invocations.
Apps can make online and offline calls on behalf of eligible unlicensed users, including calls from Forge resolvers and Forge Remote. Online calls use the invoking user’s context, while offline calls can act on behalf of a specified user where supported.
Existing Forge app permissions, product permissions, and API-specific access controls continue to apply. This change does not enable anonymous-user access.
This includes support for eligible unlicensed users accessing apps through the Jira Service Management portal.
The Atlassian Rovo MCP Server is adding six new Jira Align tools through MCP V2 across two new toolsets: read_jira_align and write_jira_align. These tools enable AI agents and workflows to interact directly with Jira Align data for portfolio reporting, planning rollups, terminology discovery, and backlog hygiene.
Tool | Description |
|---|---|
| Get the organization’s Jira Align terminology, including customized names for entities and fields. |
| Discover valid fields, allowed values, required fields, and filtering capabilities for a Jira Align item type. |
| Get a Jira Align item by its numeric ID and item type, with optional related-item expansion. |
| Search and list Jira Align items by type using field selection, filters, ordering, expansion, and pagination. |
| Create a Jira Align item using fields and requirements configured for its item type and portfolio. |
| Update selected fields on an existing Jira Align item. |
Jira Align tools in MCP V2 support OAuth 2.1:
Read tools belong to the read_jira_align toolset and require the read:jira-align:agent-interface scope.
Write tools belong to the write_jira_align toolset and require the write:jira-align:agent-interface scope.
Admin enablement: Organization Admins must enable the Jira Align toolsets in Admin Hub under Security > Data protection > Atlassian Rovo MCP server (or MCP tool settings) before users can access them.
Re-authorization: Users will need to re-authorize or reconnect their MCP client to grant the new Jira Align scopes.
Requirements: Requires Jira Align Cloud, Atlassian Guard enabled, an active Jira Align Bridge mapping connecting the sites, and the user to have logged in to the Jira Align UI at least once.
Tool availability depends on granted scopes, the permission groups enabled by your organization admin, and your app access. For details on these tools, please refer to our https://developer.atlassian.com/cloud/rovo-mcp/guides/supported-tools/ documentation.
The Forge global:ui module has moved from the Early Access Program (EAP) to Preview. You can now build apps that look and feel like Atlassian core products, featuring configurable side navigation and a dedicated entry in the Atlassian app switcher.
What’s changing
Increased sidebar customization: New components are available for the sidebar, including MenuSection, MenuSpacer, ReorderableMenuItems, SidebarFooter, and SearchableFlyoutMenuItem. You can also use UI Kit and custom icons.
Relevant search results: The Rovo search bar now prioritizes results from Teamwork Graph objects associated with the global:ui app you are viewing.
Custom search results pages: Pressing Enter in the search bar now navigates to your app’s /search?text=<input> route, allowing you to build a custom search results experience.
Compatible with all installation models: The global:ui module is now compatible with site, cross-context, and unit-level installations.
What you need to do
Review the global:ui documentation to understand the module's capabilities.
Explore the component reference for details on the new sidebar components.
Learn more about ingesting Teamwork Graph objects to improve search relevance for your app.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-154-ui-modifications-for-forge-custom-fields-in-jira-and-jsm/103577
Rollout : progressive rollout by tenant. IN PROGRESS
We’re excited to announce that the below Confluence suggested edits tools have been added to Confluence on Atlassian MCP. Users who have previously approved access to the respective toolsets will start to see availability of these tools shortly as the feature is progressively rolled out.
write_confluence:
addConfluenceContentSuggestions
read_confluence:
getConfluenceContentSuggestions
For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.
Rate this page: