As of Oct 9, 2025, we’ll be moving the location of the configuration for JSM approvals in company-managed projects from status properties to a new approvalConfiguration property on the status. The following endpoints will be affected:

• Bulk get workflows

• Bulk create workflows

• Validate create workflows

• Bulk update workflows

• Validate update workflows

Refer to CHANGE-1656 for more details.

Forge platform will be undergoing maintenance in commercial production on October 12, 2025 for approximately 1 minute between 3-4am UTC

During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

Starting Mar 31, 2026, the ability to update existing Jira or Confluence apps using a Connect descriptor on the Atlassian Marketplace will be deprecated. This change aligns with our strategic shift to the Forge platform.

Additionally, this means the following:

1. Atlassian Marketplace will no longer poll for Connect descriptor updates. However, apps using Connect modules that have adopted the Forge manifest can still receive updates.

2. Installing new Connect private apps via Connected Apps will no longer be available and private app development should move to Forge.

What this means for partners:

1. Partners should plan to update Connect apps on the Atlassian Marketplace by Mar 30, 2026 at the latest.

2. All new app development should be conducted on Forge.

You can now add and edit configuration for function validators in the new workflow editor. This update lets you save configuration data and pass it to the lambda function under the configuration parameter during invocation. This makes it easier to customize and manage workflow validation logic.

For more information, see Jira Workflow Validator.

We're introducing new App Property API endpoints to retrieve Forge App Properties in Confluence & Jira, now available in Preview.

The APIs enable developers to

• GET all Forge app properties, or

• GET individual app properties by key

in both Jira and Confluence, enhancing the flexibility and functionality of Forge apps.

For further details on implementing this new feature, refer to the Jira App Property API Documentation & Confluence App Property API documentation.

Following a recent incident (see details), we have temporarily paused automatic Connect to Forge migrations. Our team is actively working to enhance system robustness and prevent similar issues from occurring in the future.

Once these improvements are complete, we will re-enable and resume the migration process.

Following our prior deprecation notice, you can no longer publish a new Jira or Confluence app using a JSON Connect descriptor to the Atlassian Marketplace.

From now on, all Atlassian Marketplace apps should be built using Atlassian’s Forge platform.

Forge platform will be undergoing maintenance:

• in FedRAMP production on September 21, 2025 between 5-6am UTC

• in commercial production on September 28, 2025 between 5-6am UTC

During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

The allow-popups attribute of the sandbox directive (content security policy) is now supported in Forge Custom UI and UI Kit apps when using * as your client egress configuration. This enables external content (such as those from 3rd party integrations) to open properly in new tabs instead of being blocked by browser security restrictions.

With this enhancement, external content will open in a new browser tab while keeping your Forge app running.

For more information, see the valid domain formats documentation.

We are releasing a Workflow Preview API that offers read-only access to workflow configurations. This API supports the current workflow view for work items within a project context. The preview includes nearly all the content of the full workflow but limits exposure of rule configurations and status properties. It is also available to users with View (read-only) workflow permissions.

To support Jira performance at scale, we are introducing a limit on how many work types and how many fields can be associated to a company-managed project in Jira cloud:

• The admin user interface and related APIs will restrict the association of more than 150 work types to a single work type scheme.

• Similarly, they will also limit the association of more than 700 fields within the single field configuration scheme.

The limit will be effective starting Feb 9, 2026.

Exemption which will be allowed to go over these limits. Examples include:

• Installing a new app

• Enabling a new product

• Upgrading (or downgrading) a license tier

• Creating a new project

• Migrations

Jira Admins will have access to streamlining tools designed to eliminate unused fields and work types. This initiative aims to ensure that the field configuration scheme and work type scheme remain within the established limits.

Support documents

• This is building on top of what we announced in https://community.atlassian.com/forums/Jira-articles/Announcement-Changes-to-field-and-work-type-configuration-in/ba-p/3023478

• Fields https://support.atlassian.com/jira-cloud-administration/docs/optimize-fields-in-your-project/

• Work types https://support.atlassian.com/jira-cloud-administration/docs/optimize-work-types/

The following APIs will be impacted:

• Add work type to a work type scheme: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-type-schemes/#api-rest-api-3-issuetypescheme-issuetypeschemeid-issuetype-put will return HTTP 400 if the scheme is over a limit

• Create issue type scheme: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-type-schemes/#api-rest-api-3-issuetypescheme-post will return HTTP 400 if the issue type count is over a limit

• Assign work types to field configurations: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-field-configurations/#api-rest-api-3-fieldconfigurationscheme-id-mapping-put will return HTTP 400 if the scheme is over a limit

Atlassian is introducing burst API rate limiting for Jira Cloud to enhance reliability and performance. This industry standard approach helps prevent service disruptions by controlling excessive API requests from apps and scripts using API tokens, ensuring a smoother experience for all users.

On Jul 28, 2025, we announced the addition of number field formatting through the Atlassian GraphQL Gateway (AGG) for company-managed projects in Jira.

We’ll start progressively rolling out this change to each tenant today (Aug 27, 2025). We expect to finish this rollout on Sep 11, 2025.

Following our previous announcement, eligible apps migrating from Connect to Forge will now automatically roll out to customers. Rollouts will occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.

Apps which have previously adopted Forge from Connect and have not opted in to minor updates will be progressively migrated in the coming weeks.

See https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-forge-updates-preview/ for details about eligibility. To test and validate your app’s migration process, you can still opt-in to the staged migration process.

We're reminding developers that the "Myself-> Set locale" API was previously marked as deprecated. This API is being deprecated because user management is now handled through the Admin Hub, not within Jira.

This change will take effect on Feb 14, 2026.