This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Service Management Cloud.
Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes that affect all users of the Jira Cloud products are announced.
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.
Learn more about the announcement of our timelines for the end of support for Connect. Existing apps built with Connect should explore https://developer.atlassian.com/platform/adopting-forge-from-connect/.
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 announcing support for the following Forge Jira Software provider modules. More information can be found in our documentation: https://developer.atlassian.com/platform/forge/manifest-reference/modules/index-jsw/
devops:developmentInfoProvider
devops:featureFlagInfoProvider
devops:deploymentInfoProvider
devops:buildInfoProvider
devops:remoteLinkInfoProvider
The following UI Kit components are now generally available:
https://developer.atlassian.com/platform/forge/ui-kit/components/adf-renderer/
https://developer.atlassian.com/platform/forge/ui-kit/components/calendar/
https://developer.atlassian.com/platform/forge/ui-kit/components/checkbox-group/
https://developer.atlassian.com/platform/forge/ui-kit/components/empty-state/
https://developer.atlassian.com/platform/forge/ui-kit/components/inline-edit/
https://developer.atlassian.com/platform/forge/ui-kit/components/list/
https://developer.atlassian.com/platform/forge/ui-kit/components/popup/
https://developer.atlassian.com/platform/forge/ui-kit/components/time-picker/
No code changes are required. These components will now follow the 6 month deprecation period if any breaking changes were to be made.
We've introduced support for all Forge custom field types on the Jira Service Management portal view. This update allows you to specify the portal-view experience in the view entry point when using UI Kit for app rendering. The goal is to improve the flexibility and functionality of custom fields in the Jira Service Management portal.
Additionally, Forge custom fields on Jira Service Management portal requests are now generally available.
We're also introducing unlicensed access support for Forge custom fields on the Jira Service Management portal. Documentation for it can be found here: https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-jsm-users/.
For more information on Forge custom fields, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/ or https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type/
As part of the Atlassian visual refresh updates, we updated the UI Kit Icon component. Some glyphs get a new look, and many more glyphs have been added. There are also a number of deprecations, as detailed below.
The size prop will only support the values "small" and "medium". The value "large" is now deprecated and will be removed.
The prop primaryColor has been renamed to color.
The prop secondaryColor is now deprecated and will be removed.
Some glyphs haven been replaced and others will be removed. Visit the Icon migration guide for information on finding a replacement.
The new default size for icons will change from 24x24 pixels to 16x16 pixels.
All deprecations and breaking changes will take place on Jan 1, 2026. Until then, the new Icon component will be fully backwards-compatible. Any deprecation will trigger a console warning prefixed with [@forge/react: Icon] on non-production environments.
Forge Remotes are now available in the Atlassian Government Cloud. Please refer to the AGC documentation for details on supporting Forge Remotes within your AGC Forge app.
We’re introducing the ability for apps to publish events, allowing for enhanced interoperability between apps. This feature enables apps to subscribe to events using the existing https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/ module, opening up new possibilities for app interactions.
Developers can start using app events by implementing the https://developer.atlassian.com/platform/forge/manifest-reference/modules/event/ module in their apps. For detailed guidance and examples, refer to https://developer.atlassian.com/platform/forge/events-reference/app-events/.
To publish events using the runtime API, you need at least version 2.0.0 of the @forge/events dependency. Add this to your package.json:
1
2
3
4
5
{
"dependencies": {
"@forge/events": "^2.0.0"
}
}We have enhanced Bulk Move API to allow users to move both parent and child work items/issues in a single request, as well as move multiple work items/issues of different types in the same request.
Starting on September 29, 2025, the JSM Create organization public API, will no longer sanitize the name value, and will instead perform an exact match on the name value supplied by the caller while finding an existing organization by name.
JSM will also start applying a new validation rule when creating new organizations. Requests in which the name field contains extra whitespaces at the start, end or in-between, will fail with an HTTP 400 code.
Valid name examples: Test organization , Support User Group
Invalid name examples: Test organization , Support user group
The JSM Create organization public API currently sanitizes the supplied ‘name’ value by removing extra whitespaces at the start, end, or in between. Going forward, we’re making the following changes to the sanitization and validation logic for the name field from the request body.
Current behavior:
The value of the name field in the request body can contain extra whitespaces at the start, end, or in between. JSM sanitizes the name and creates a new organization if an organization with the sanitized name doesn’t already exist. (Example: My org is considered a valid name and will be sanitized to My Org while getting existing or creating a new organization).
New behavior:
JSM won’t sanitize the name value and will find the existing organization for the exact name value sent by the caller.
If the existing organization isn’t found, JSM’ll apply the new validation rule below and create a new organization only if the validation passes.
New validation rule: Check for extra spaces in the name value, and fail the request with a 400 Bad Request error if there’re extra whitespaces at the start, end, or in between. (Note: A single in-between whitespace is valid; for example, test organization is valid.)
Reasons for this change:
We’re rolling out the JSM SCIM provisioning feature which allows admins to manage customer organizations in external IdP and provision them to JSM. Custom sanitization logic for names can’t be applied for organizations synced from external IdP since JSM is expected to match the exact value of the organization name from IdP.
The new validation rule is required to ensure that a new organization doesn’t get created inadvertently for existing public API callers who rely on sanitization logic to remove whitespaces and find an existing organization on their JSM site.
Ways to fix your app or caller program:
Remove leading, trailing, or multiple in-between whitespaces while creating a new customer organization.
Send an exact match for the name field (without additional whitespaces) if you intend to get the existing organization by name.
We have published a new migration guide to assist you in transitioning your Forge custom fields to use the isInline property.
The guide includes two practical examples:
Migrating a Forge custom field to render inline
Migrating a Forge custom field to render in a modal
For more details, please refer to https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#inline-edit-migration-guide
Blob objects can now be sent and received via the events API. This enhancement allows for more efficient data handling and transmission within the API.
Update to the latest version of @forge/bridge with npm install --save @forge/bridge@latest
We’ve added additional project information to the extension context for Forge custom fields on Jira Service Management portal requests. This allows accessing project.id directly from the extension data to avoid unnecessary REST API calls.
Rate this page: