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.
Forge TypeScript bundler, previously available as an EAP, has been removed. Use manual packaging, now available in preview, instead, running your own tsc (or a different compiler).
Manual packaging is a more flexible replacement for the TypeScript bundler. It lets developers choose an arbitrary build tool, and supports UI Kit modules in addition to the runtime bundling.
Confluence Cloud will enforce approval-required publishing for direct page updates made through the Confluence REST APIs. In spaces where admins require approval before publishing, direct updates to published pages will return HTTP 409 Conflict. Integrations must save changes as a draft, complete the approval, and publish the approved draft.
This affects PUT /wiki/rest/api/content/{id}, PUT /wiki/api/v2/pages/{id}, and PUT /wiki/api/v2/pages/{id}/title. It applies only to regular pages in spaces configured to require approval; other spaces and content types remain unchanged. We will update this entry with the rollout date before enabling the change.
Manual packaging for Forge functions and UI Kit modules has progressed from the Early Access Program (EAP) to Preview. Manual packaging lets you bypass the fixed version of Webpack bundled within the Forge CLI and upload your code directly from specified directories without modification.
What's changing
Manual packaging is now suitable for production environments, and you no longer need to sign up for the EAP to use it. With manual packaging, you can:
Use a different compiler or TypeScript version.
Use alternative bundlers (such as Vite or Esbuild) or no bundler at all.
Include and call WebAssembly in your application.
Require data files or depend on packages that do.
Reduce application size by sharing dependencies across multiple functions.
What you need to do
If you were already using manual packaging during the EAP, no changes are required.
To get started, set bundler: manual@2026 and a path in the app.package section of your manifest for functions, or on individual UI Kit resources.
For details and examples, see Packaging and the Packaging standard.
The rovo:agentConnector module is now Generally Available (GA). This module lets you connect an AI agent hosted outside of Forge to Rovo using the Agent2Agent (A2A) protocol, so your agent can be used alongside native Rovo agents. Only A2A 1.0 is supported.
🛠️ Scheduled maintenance window from September 25 @ 5PM PST to Monday, September 28 @ 10AM, AEST
Our support portal is moving to a new home. New ticket submissions and ticket access including comments via email will be unavailable during this window. Starting September 28, submit all requests at Atlassian Support and update your bookmarks. Learn what's changing.
We’re excited to announce that getJiraWorkflowEditorLink has been added to manage_jira on Atlassian MCP. Users who have previously approved access to manage_jira will start to see availability of this tool shortly.
For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.
We’re excited to announce that getJiraWorkflows has been added to manage_jira on Atlassian MCP. Users who have previously approved access to manage_jira will start to see availability of this tool shortly.
For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.
We’re excited to announce that createJiraIssueRemoteIssueLink has been added to write_jira on Atlassian MCP. Users who have previously approved access to write_jira will start to see availability of this tool shortly.
For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.
We’re excited to announce that convertJiraIssueHierarchy has been added to write_jira on Atlassian MCP. Users who have previously approved access to write_jira will start to see availability of this tool shortly.
For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.
The tool editJiraIssue as part of the write_jira toolset has been updated.
Three optional input fields have been added: rankBeforeIssue, rankAfterIssue and rankCustomFieldId. They rank the work item directly above or below another work item on a board or backlog. rankCustomFieldId selects the rank field when a board uses a custom one.
The tool listJiraIssueComments as part of the read_jira toolset has been updated.
An optional input field reactionDetail has been added, with the values none, summary and users. none (the default) returns comments only. summary adds emoji reaction counts and whether the current user reacted. users also names who reacted.
The tools searchJiraIssuesUsingJql as part of the search_jira toolset and getJiraBoardIssueData as part of the read_jira toolset have been updated.
The optional input field validation has been removed from both tools. Requests that still include it continue to work; the field is ignored.
What’s changing?
In preparation for the upcoming Developer Preview release of Forge Static Macros, access to the early access program (EAP) for this capability is now closed.
We want to thank everyone who participated in the EAP and provided valuable feedback. Your insights have been instrumental in shaping the next phase of Forge Static Macros.
What you need to do
If you are currently participating in the EAP, you can continue to use the feature.
If you missed the EAP, stay tuned to this changelog for the Developer Preview release announcement to start building with Forge Static Macros.
Rollout: progressive rollout by tenant. IN PROGRESS
Upgrading a Connect app installation to a Forge-only version previously called the Connect uninstalled lifecycle hook before the Forge installation event fired. This was indistinguishable from a customer uninstalling the app.
The uninstalled hook is now suppressed for both migration paths:
an already-harmonised (Connect on Forge) app installation upgrading to a Forge-only version
a Connect app installation upgrading directly to a Forge-only version under the same app key
Rollout : progressive rollout by tenant. IN PROGRESS
What’s changing
We’ve introduced new tools for individual capacity planning in the Atlassian Model Context Protocol (MCP). These tools allow you to interact with capacity plans directly through AI-powered interfaces using the read_capacity_planning and write_capacity_planning toolsets.
The new toolsets include 5 tools that enable you to:
View individual team member allocations.
Manage work allocations across projects and work items.
What you need to do
If your organization uses auto-enablement for toolset groups, these tools may not be immediately available to all users. Admins can manage access and enable these toolsets through the Atlassian MCP section in the Admin portal.
For more information on how to use these tools, see the supported tools documentation.
Rate this page: