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.
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
We are sunsetting SSH access via bitbucket.org in favor of ssh.bitbucket.org. This is an important change to improve Bitbucket’s security posture and safeguard our customers from denial of service abuse. We have originally announced this change on May 12, 2026 in Changelog announcement. We will be running a series of brownouts to help teams identify and mitigate any remaining usage of the old hostname.
For the brownout schedule and additional details refer to community blogpost.
During each brownout window, we will:
Temporarily block SSH traffic on bitbucket.org
Show clear error messages
Show in-product messaging to create awareness
What's changing
We're introducing a new sharing level for Forge and OAuth 2.0 (3LO) apps: organization-level sharing. With it, you can share your app with anyone in the same Atlassian organization as the app owner.
Key details:
Restricted installation: Only members of the app owner's organization can install the app using the installation link.
Existing installations: If you change a publicly shared Forge app to organization-level sharing, existing installations on sites outside your organization will keep working.
Upgrade restrictions: For apps updated to organization-level sharing, future app upgrades will only be available to members of the app owner's organization. Installations outside the organization stay on the current version unless upgraded by the app developer.
What you need to do
To use this new sharing level:
Navigate to the Developer Console and select your app.
Select Distribution from the left menu.
Under Distribution controls, select Edit.
Choose the Sharing within organization option and save your changes.
For more information on app distribution, see the distribute your apps documentation.
The tool listJiraIssueComments as part of the read_jira toolset has been updated.
It is now a primary tool: it is returned directly in the MCP tools/list response and can be called by name, alongside getJiraIssue, searchJiraIssuesUsingJql, createJiraIssue, editJiraIssue, transitionJiraIssue and addOrEditJiraIssueComment. Previously it was a deferred tool, reachable only through discover followed by executeRead. It no longer appears in discover results; discover lists it under primaryTools instead, and calling it through executeRead continues to work.
Inputs, outputs, toolset and the read:jira:agent-interface scope are unchanged.
Starting February 1, 2027, we'll progressively roll out a change to the portfolioChildIssuesOf() JQL function so its results include work items in team-managed spaces. Today, the function only follows hierarchy in company-managed spaces, so searches can miss descendants that live in team-managed spaces.
portfolioChildIssuesOf() will return descendants through valid team-managed space hierarchies, including supported relationships between company-managed and team-managed spaces, such as a team-managed epic under a company-managed initiative.
Queries that use NOT IN portfolioChildIssuesOf() will exclude these additional work items.
Results continue to respect hierarchy rules, user permissions and issue security.
REST API request and response formats don't change.
If your app, saved filters or automation rules assume that team-managed work items are excluded from portfolioChildIssuesOf() results:
Find the queries that use portfolioChildIssuesOf().
Check whether team-managed work items in the results would affect your logic.
If they would, update your queries or result handling before February 1, 2027.
We'll publish another update when the rollout starts.
What's changing
We've updated the minimum compatible Node.js version for the Forge CLI. The CLI now requires Node.js 22.23.4, 24.22.1, 26.12.1, or newer.
Node.js 20 has reached end of life and is no longer supported. To continue using the Forge CLI to develop and deploy your apps, you must upgrade your local development environment to one of the supported versions listed above.
What you need to do
Check your current Node.js version by running node -v in your terminal.
If you are running a version older than the requirements, download and install a supported version from the Node.js website.
Update your Forge CLI to the latest version by running:npm install -g @forge/cli@latest
Verify the installation by running forge --version.
For more information on setting up your development environment, see the Getting started guide.
Following the previous deprecation announcement, we will begin scheduled brownouts of the Bitbucket Cloud Code Search API on 3 November 2026 at 00:00 UTC.
Brownouts are temporary periods when the API is unavailable, intended to help you identify integrations that still need to migrate. The brownout duration will progressively increase before the API becomes permanently unavailable on 15 November 2026 at 00:00 UTC.
Migrate your integrations to the workspace code search API before the brownouts begin.
/2.0/users/{user}/search/code
/2.0/teams/{team}/search/code
/2.0/workspaces/{workspace}/search/code
All dates and times are in UTC. Brownouts start at 00:00 UTC each day and repeat every 6 hours. The duration below applies to each brownout window.
Date | Brownout duration | Start time (UTC) |
|---|---|---|
November 3, 2026 | 15 minutes | 00:00, 06:00, 12:00, 18:00 |
November 4, 2026 | ||
November 5, 2026 | 1 hour | |
November 6, 2026 | ||
November 7, 2026 | 2 hours | |
November 8, 2026 | ||
November 9, 2026 | 3 hours | |
November 10, 2026 | ||
November 11, 2026 | 4 hours | |
November 12, 2026 | ||
November 13, 2026 | 5 hours | |
November 14, 2026 | ||
November 15, 2026 onwards | Permanently unavailable | |
During brownouts, requests to the affected endpoints will return HTTP 410 Gone, with an error message linking to the replacement API documentation. Outside the scheduled brownout windows, the deprecated endpoints will remain available until permanent removal.
Update applications, scripts, and integrations that use the affected endpoints to use:
POST /2.0/workspaces/{workspace}/codesearch
The replacement API uses a different HTTP method and request format, so migration requires more than changing the endpoint URL. Review the workspace code search API documentation and update your integration before 3 November 2026 to avoid disruption.
We understand these changes require effort, and we're here to support you. If you have questions, need migration guidance, or run into issues, please contact Atlassian Support.
As of October 16, 2026, the following legacy Loom MCP tools are no longer returned to users in the Loom V2 rollout cohort.
Use these replacement tools:
listLoomVideos and listLoomVideosSharedWithMe → listLoomObjects
getLoomVideo → getLoomObjectsContent
getLoomVideoComments and getLoomMeetingActionItems → getLoomObjectsContent with the applicable content expansion
createLoomVideoComment and createLoomVideoReaction → addLoomInteraction
updateLoomVideoTitle → updateLoomObjectMetadata
updateLoomVideoPermissions → updateLoomObjectVisibility=
shareLoomVideo → shareLoomObject
createLoomVideoUpload → createLoomObjectUpload
publishLoomVideo → publishLoomObject
listLoomFolders → listLoomObjectFolders
createLoomFolder → createLoomObjectFolder
moveLoomVideoToFolder → moveLoomObjectToFolder
Compatibility for getLoomVideo
getLoomVideo is unlisted rather than immediately disabled. New tool-list responses do not advertise it, but existing sessions that cached its schema can continue calling it during the compatibility period. New integrations should use getLoomObjectsContent.
Tools that remain available
getLoomVideoDownloadUrl and recoverLoomVideo are not replaced by this migration.
This is the removal half of the coordinated Loom MCP V2 migration announced in CHANGE-3503.
Rate this page: