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.
You can now set custom colors for UI Kit Visualisation charts. You can either set a color theme or assign colors to attributes. This can be done by passing the prop colorPalette into your chart.
For an example of how to implement this, please see the Forge UI Kit example app at https://bitbucket.org/atlassian/ui-kit-charts-example/src/master/.
For more information, see documentation.
Jira global background scripts are now available in Preview. This feature enables you to add an invisible container that coordinates data and behavior across all pages in Jira, enabling advanced integrations and automations.
We’re releasing this feature in preview to gather feedback and help you prepare for upcoming changes. You can use global background scripts in production environments during the preview period.
For more information, see Jira global background scripts (Preview)
As announced in July 2025, a number of glyphs for the Icon component will now be removed.
This fix will be rolled out on Jan 28, 2026 across all Jira Cloud instances.
We fixed bugs that caused the Issues Match REST API and webhooks to evaluate JQL queries differently than the standard Issue Navigator. JQL expressions using EMPTY or != with issue properties or the "Epic Label" field now return consistent results across all Jira Cloud features.
This fix is not backward-compatible. Integrations that relied on the previous behavior may see different results from the Match API or different events triggering webhooks.
Related tickets: JRACLOUD-96922, JRACLOUD-97120
JQL expression | Previous behavior (Match API/webhooks) | New behavior |
|---|---|---|
| Did not match issues where the field was unset | Matches issues where the field is unset |
| Matched correctly | No change |
| Did not match issues where the field was unset | Matches issues where the field is unset |
| Matched all issues, including those where the field was unset | Only matches issues where the field is set |
| Matched correctly | No change |
| Matched all issues, including those where the field was unset | Only matches issues where the field is set |
This applies to both issue properties (for example, issue.property[key].path) and the "Epic Label" field.
JQL expression | Previous behavior | New behavior |
|---|---|---|
| Returned issues where the property was never set | Only matches issues where the property exists and its value is not |
You may see differences in:
The issues returned by POST /rest/api/3/match when using JQL with EMPTY or != on issue properties or "Epic Label"
The events that trigger webhooks using JQL filters with these operators and fields
Review any JQL used in webhook filters or Match API requests that contains:
EMPTY operators with issue properties or "Epic Label"
!= comparisons with issue properties
Best practices:
Goal | Recommended JQL |
|---|---|
Check if a field is set |
|
Check if a field is not set |
|
Specific scenarios:
To find issues where a property is either not set OR has a different value:
1
issue.property[key].path != "a" OR issue.property[key].path IS EMPTYTo find issues where a property is set AND has a different value:
1
issue.property[key].path != "a" AND issue.property[key].path IS NOT EMPTYTest critical webhook flows and integrations that use the Match API to confirm they behave as expected.
You can now use UI modifications with Jira Service Management (JSM) request create portal view. This is an extension of the existing jira:uiModifications module, allowing you to change the look and behaviour of JSM request create portal view. The module is designed to be used in conjunction with the UI modifications (apps) REST API.
For more information, see the JSM UI modifications module documentation.
The following UI Kit components are now generally available:
Comment, which displays discussions and user feedback.
Pressable, which is a primitive for building custom buttons.
CommentEditor, provides a contained comment editor UI with a simple toolbar.
ChromelessEditor, provides a simple text editor that does not have a toolbar.
For more information, see the component documentation.
To access these components, you will need to update your app to the latest version of @forge/react. In the terminal of your project directory, run:
npm install --save @forge/react@latest
We've introduced an experimental REST API endpoint that lets site admins revoke portal-only access for a specific user. After revocation, the user won't be able to log in to the Jira Service Management customer portal as a portal-only user, and they will also be unable to submit or view requests through the portal.
This API was developed in response to JSDCLOUD-8533.
For more information, see Revoke portal only access for user API.
The operation accepts the Atlassian account ID of the user whose portal-only access you want to revoke.
Only site admins (members of the site-admin group) can use this API.
Endpoint: PUT /rest/servicedeskapi/customer/user/{accountId}/revoke-portal-only-access
Currently, the new workflow editor is the default editing experience in Jira and is being used by the majority of customers.
Starting 26th June 2026, we will begin removing the old workflow editor for customers, which means workflows will only be editable in the new workflow editor. We ask you to please help your customers in this transition by ensuring that any workflow-related apps will work effectively with the new workflow editor.
If you encounter any issues with how your apps behave in the new workflow editor, please raise a support ticket.
Some features to be aware of to improve app experiences in the new editor:
Dynamic configuration descriptions (Forge/Connect)
Make sure to provide a unique description for configured rules.
Additional context (Forge/Connect)
Determine whether the rule is loaded in the new or old workflow editor.
Default workflow editor for user (API)
Determine whether a user has a preference set for the new or old editor.
Deep linking to statuses and transitions
Link to the new workflow editor and provide an ID with either the selectedStatus or selectedTransition query params to pre-select a status or transition.
Following the Preview release, the Forge Automation Actions is now generally available. The Automation action module allows you to extend the Automation Platform and add new Forge-based actions to your app. With this release Forge Actions can now output smart values, enabling seamless data flow and dynamic automation.
For more information, see the Forge Automation Action module documentation.
Forge platform will be undergoing maintenance in commercial production on November 23, 2025 for approximately 1 minute between 5:30-6:30am 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 sidebar will now span the full height of your Atlassian app, making it easier to find and interact with. Starting late November 2025, this update will roll out to all customers who haven’t customized the look and feel of their sites. This change won’t affect the width and height of your Forge and Connect apps.
Along with this, we’re introducing a few improvements to sidebar interactions:
Double-click to collapse: When expanded, double-click the button to quickly collapse the sidebar.
Global shortcut: Use Ctrl + [ to expand or collapse the sidebar at any time.
Helpful tooltips: Tooltips will appear to guide you through the interaction.
For sites with customized look and feel, the full-height sidebar can disrupt intentional design choices, such as:
Custom logos and titles
Favicons
Navigation colors
Dark and light mode settings
Because of this, the sites with customized look and feel won’t receive the update just yet.
For the sites without customized look and feel, we’re opening up the opportunity on Nov 21, 2025 to let you use this feature early and test it with your apps. If you’re interested, please sign up here with your site details.
You can now provide dynamic descriptions for the configuration of Forge workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.
Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.
You can now enable your Forge workflow conditions, validators and post functions in team-managed workflows. Use the projectTypes property to configure whether your rule should be enabled for company-managed projects, team-managed projects, or both.
You can now provide dynamic descriptions for the configuration of Connect workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.
Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.
When defining resolvers, the front-end code can share the types with the backend so the invocation interface is type-safe. This helps catch potential errors during compilation.
Rate this page: