Atlassian developer changelog

We're adding v2 versions of two Marketplace search reports: top search keywords and zero search results keywords.

Beginning June 12, 2026, non-essential cookies and tracking technologies were disabled by default for Marketplace users from regulated regions, and users there must now opt in to cookies before analytics data is collected. Because these reports were built from browser analytics, reported search volumes dropped for affected traffic.

The v2 reports count searches recorded by Marketplace search itself, so they include every search regardless of a user’s cookie choices.

Two new endpoints are available, each with a matching /export variant:

GET /rest/3/reporting/developer-space/{developerId}/search-keywords-v2/source/{sourceKey}
GET /rest/3/reporting/developer-space/{developerId}/zero-search-results-keywords-v2/source/{sourceKey}

Please note that the updated counts are only available post 25th Sept 2026. Earlier dates would still have data only for users who consented for tracking cookies.

• The existing endpoints are unchanged and remain available for now but will be removed soon.

• Query parameters, authentication, and the response format are identical between the two versions, so moving to v2 only requires changing search-keywords to search-keywords-v2, or zero-search-results-keywords to zero-search-results-keywords-v2, in the path.

• Source coverage is also unchanged. The search keywords report supports marketplace and embedded-marketplace, and the zero search results report supports marketplace only.

• Review your reporting. If you track search counts over time, expect a step change when you switch.

• Historical data is limited. v2 data is available from 25th Sept 2026. Earlier dates would still have data only for users who consented for tracking cookies.

We’re excited to announce that organization admins can now set up the Atlassian Rovo MCP server control in Data Security Policy. Admins can govern how external AI tools read and write Jira and Confluence data using MCP, with org-wide defaults and overrides scoped by Atlassian apps, spaces, and classification levels. It works the same way as existing DSP controls like data export, anonymous access, and public links.

To get started:

1. Go to Atlassian Administration. Select your organization if you have more than one.

2. Select Security.

3. Select Data protection, then select Data security policies.

4. Edit the Atlassian Rovo MCP server control.

For more details read our documentation.

You can now use display conditions to hide sub-pages or sections in several Jira Forge modules. This allows you to show or hide UI elements based on specific criteria, such as user permissions or project types.

The following modules now support display conditions on their pages and sections child properties:

• jira:adminPage

• jira:globalPage

• jira:projectPage

• jira:projectSettingsPage

• jira:personalSettingsPage

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).

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.