Atlassian developer changelog

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.

New experimental APIs let you list, grant, and remove organizations’ access to an organization-restricted Customer Experience.

Customer profile and bulk APIs now accept eligible Atlassian Accounts as customers. You can retrieve their profiles and update their detail fields, organization associations, and product associations using their Atlassian account ID as customerId. The account must be active, have the CSM Customer role, and be neither a CSM agent nor a Jira site admin. Customer Account creation and lifecycle APIs continue to manage Customer Accounts only.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-148-local-forge-storage-prototype-for-kvs-and-sql/102858

We’re upgrading Jira dashboards to a more modern and flexible experience. As part of this transition, we’re deprecating the legacy Forge modules for dashboards in favor of these new dashboard modules.

What’s changing
The following Forge modules are now deprecated and will be removed on May 17, 2027:

• jira:dashboardGadget

• jira:dashboardBackgroundScript

These modules are replaced by the new dashboards:widget and dashboards:backgroundScript modules, which are now General Availability (GA). The new modules are designed for the upgraded Jira dashboard surface (also referred to as AVP dashboards).

What you need to do
To ensure your dashboard extensions continue to work on the new Jira dashboard experience, you must migrate your existing modules:

1. Update your app manifest to use the new dashboards:widget and dashboards:backgroundScript modules.

2. Complete your migration before the deprecation date of May 17, 2027 to avoid service disruption for your users.

What’s changing

The new Forge dashboard modules are now generally available (GA). These modules allow you to build extensions for the upgraded Jira dashboard experience, which offers a more modern and flexible interface for users:

• dashboards:widget: Used to create custom content blocks (widgets) on the new dashboard surface.

• dashboards:backgroundScript: Used to run background logic for your dashboard extensions.

The new Jira dashboard experience, which utilizes these modules, is rolling out to customers starting September 23rd, 2026.

What you need to do
You can now start building and deploying apps using these modules for the new Jira dashboard experience:

1. Review the dashboards:widget manifest reference for configuration details and schema.

2. If you have existing dashboard extensions using the legacy jira:dashboardGadget or jira:dashboardBackgroundScript modules, you should begin planning your migration to these new modules.

3. Note that the new dashboard experience coexists with classic Jira dashboards during the rollout period.

The tool findJiraIssueAssignableUsers as part of read_jira toolset has been updated.

The tool has now been renamed to listJiraIssueAssignableUsers

What's changing
We are updating how Forge permission checks are implemented in Jira for asApp requests. This internal change simplifies the evaluation process and removes the requirement for permissions to be synced to Jira at installation time.

This update improves the app installation process by reducing the overhead associated with permission synchronization.

What you need to do
No action is required from you. This is an internal implementation change that does not affect how you declare permissions or use asApp in your Forge apps.

The update is being rolled out progressively on a tenant-by-tenant basis.

Marketplace partner reports are currently missing invoice data for September 15–17, 2026 due to a data ingestion delay. The underlying issue has been resolved, and data is actively backfilling.

Starting September 15, 2026 at approximately 12:00 PM IST (06:30 UTC), a data ingestion service encountered a memory-related issue, resulting in recurring job restarts. This created a processing backlog of approximately two days, temporarily preventing invoice events from syncing to Marketplace partner reporting.

Invoice and transaction records in Marketplace partner reporting are incomplete for September 15-17, 2026. This impacts:

• Vendor report UI: Daily/monthly sales and revenue summaries.

• Transaction exports: Downloadable CSV/transaction detail exports.

• Reporting APIs: Responses reflecting invoice data within this date window.

• Data integrity: No data has been lost. All transactions, billing records, and refund events remain queued upstream and are processing.

• Historical data: Reports prior to September 15, 2026 are unaffected.

• Other services: All other Marketplace APIs, listing pages, and developer surfaces are operating normally.

• No immediate action is required. Backfilling occurs automatically.

• Once recovery is complete, we recommend re-exporting or re-fetching reports and API data for September 15–17, 2026 to ensure your local records reflect finalized figures.

We will post a follow-up update here once the backfill is complete and all reporting data is fully verified. We apologize for the inconvenience and appreciate your patience.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-147-app-custom-migration-progress/102702.

Trello now supports OAuth 2.0 authorization code grants for apps, featuring granular scopes, short-lived tokens, resource restrictions, and a redesigned consent screen consistent with other Atlassian products. New apps can opt in right away, and existing apps can transition when ready.

Read more on our developer community page - OAuth 2.0 is now available for Trello!

What's changing

The installations page in the developer console has been redesigned to scale with large app install bases. Following the EAP release, we have added two key improvements to help you manage your data:

• Additional filters: You can now use new granular filtering options to find specific installations faster.

• Sorting capabilities: We have enabled sorting for key columns to improve data discoverability.

These updates build on the core redesign, which includes optimized page performance for large datasets and the ability to customize your view by resizing, reordering, or pinning columns.

What you need to do

No action is required to enable these features; the updated installations page is now live for all Forge apps.

For more details, see View app installations. You can also share your feedback by selecting the Give feedback button in the Get help section of the developer console.

What's changing

Branch restrictions now support adding the following to Write Access and Merge Access branch permissions in your branch restriction rules:

• Repository access tokens (RAT)

• Project access tokens (PAT)

• Workspace access tokens (WAT)

• Forge apps

• Rovo Dev

This applies to both repository and project-level branch restrictions.

What you need to do

No action is required. To use this feature, navigate to Repository settings → Branch restrictions or Project settings → Branch restrictions and add your access tokens, Forge apps or Rovo Dev to the desired permission rules.

For more information see our community post.

You can now copy a workflow using the Jira Cloud platform REST API. The new copy workflow endpoint creates a new workflow from an existing one, together with the statuses that workflow uses:

POST /rest/api/3/workflows/copy

Previously, copying a workflow was only possible through the UI.

The copy is created in the same scope as the workflow it was copied from. Copying a global workflow produces a global workflow, and copying a project-scoped workflow produces a workflow scoped to the same project.

Permissions required

• Administer Jira global permission to copy any workflow, including project-scoped workflows.

• To copy a project-scoped workflow, either the Edit workflows project permission, or both the View (read-only) workflow and Administer projects project permissions.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-146-conditional-execution-for-jira-workflow-post-functions/102673/1

What's changing

We are removing support for the forge webtrigger root command to create URLs, as the deprecation window has passed. This change follows the initial deprecation announcement earlier last year.

The forge webtrigger command now requires a specific sub-command. Using the root command to generate a web trigger URL will no longer work.

What you need to do

To create a web trigger URL via the CLI, you must now use the officially supported create sub-command:

• Run the following command in your app's top-level directory:

• Follow the prompts to select your installation context and the web trigger function.

• Alternatively, you can specify the function key directly:

For more information, see the forge webtrigger create CLI reference.