Jira Service Management 11.0.x release notes

Jira Service Management Release Notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community


More

Read the Jira Service Management 11.0 upgrade notes for important details about this release and see the full list of issues resolved.

Compatible applications

If you're looking for compatible Jira applications, look no further:

Changed sorting behavior for custom fields

For: EVERYONE 

We’ve changed the sorting behavior for Assets and Organizations custom fields that support multiple values. Previously, all values were concatenated for comparison, but now only the smallest value is used which might change the order your items. Explore Assets custom fields

This change enhances sorting accuracy and consistency and affects the following custom fields:

  • Assets object

  • Assets readonly object

  • Assets object (multiple) (legacy)

  • Assets referenced object (multiple)

  • Organizations

Custom fields

Sorting order before Jira 11.0

Sorting order after Jira 11.0

Assets-related

Values were concatenated with commas. For example, an issue PUBLIC-27 with values cc and xx would be compared as cc,xx.

This resulted in ranking the issue PUBLIC-27 with value cc,xx above PUBLIC-28 with value cc,aa when sorted in descending order.

Only the smallest value is used for comparison. For example, an issue PUBLIC-27 now uses the cc value for comparison, even if it contains another value.

This results in ranking the issue PUBLIC-28 with the value cc,aa higher than the issue PUBLIC-28 with the value cc when sorted in descending order.

Organizations

Values were concatenated with spaces. For example, an issue YP-2 with values cc and xx would be compared as cc xx.

This resulted in ranking the issue YP-2 with value cc xx above YP-3 with value cc aa when sorted in descending order.

Only the smallest value is used for comparison. For example, an issue YP-2 now uses the cc value for comparison, even if it contains another value.

This results in ranking the issue YP-3 with the value cc aa higher than the issue YP-2 with the value cc when sorted in descending order.

Upgrade from ProForma Lite to ProForma full for free

For:  ADMINS

The ProForma Lite app is no longer supported. If you’re still using ProForma Lite, you can upgrade to the ProForma full app for free, keeping all your Lite forms. Explore how to switch to the full version of ProForma

Decorative separator

The following features live in the Jira Data Center platform, which means it's available for Jira Software and Jira Service Management.

End of support for the Original theme

For: END USERS ADMINS

With the new light and dark themes that brought accessibility and usability improvements, we’re removing the original theme from all products.

Advance notice: OpenSearch opt-in feature ready for early access

For: ADMINS

We’re working to introduce OpenSearch as an opt-in search engine in Jira. This will provide more advanced indexing options leading to less processing requirements and faster search results. We’re inviting you to be a part of our OpenSearch Early Access Program (EAP)! We’ve updated the OpenSearch upgrade guide to help you get started.

OpenSearch during EAP isn’t suitable for production environments, but we encourage you to try it on your testing environment and share your feedback on osfc@atlassian.com or via our customer support channel.


App signing is now enabled by default for app installations

For: ADMINS

In this release, app signing is enabled by default. This feature improves app security and was gradually rolled out across Data Center products. For details, check out this community post.

App signing affects only new app installations; already installed apps will remain intact.

The steps you need to take differ depending on whether you install applications from the Marketplace or build your custom applications.

Install apps from the Marketplace

To do so:

  1. Configure the location of the truststore folder as described in Configuring UPM app signature check.
  2. Download and install the Atlassian Certificates bundle. For details, see Updating Atlassian Certificate Bundles.
  3. That’s it! Enjoy the safe app installations from the Marketplace.

Install custom apps

If you use custom application builds, you can sign and secure your apps:

  1. Configure the location of the truststore folder as described in Configuring UPM app signature check.
  2. Get the app signature and verification certificate as described in Generating app signature and verification certificate using OpenSSL.
  3. Put your new certificate in your Trust store as described in Updating Atlassian Certificate Bundles.
  4. Install the signed application.

You can also install the app via the file system without using the app signing feature.

If you’re experiencing issues, check out app signing troubleshooting.

Check indexing stats in JMX

For: ADMINS

We’ve added indexing statistics to the In-Product Diagnostics (IPD). Previously, you could see these statistics exported in jira-stats only. Now, you can also access them through Java Management Extensions (JMX). This change simplifies the integration of indexing statistics with your existing observability tools. More about live monitoring using the JMX interface

Simplification of multipart handling in WebWork

For: ADMINS

We've removed several unused features of the WebWork library within Jira. These features weren't recommended for customization. If you've modified your webwork.properties file, ensure the following fields are set to their default values:

webwork.multipart.parser=custom
webwork.multipart.parser.class=com.atlassian.jira.web.TempFileRemovingMultipartRequestWrapper


Removal of Trusted apps

For: ADMINS

We’re removing Trusted apps to reduce the number of insecure entry points into the products. We’ve replaced this way of exchanging information between Atlassian products with more secure solutions that follow industry best practices, like the OAuth 2.0 protocol.

Before you upgrade to Jira 11.0

Platform releases allow us to incorporate multiple significant changes (often called breaking changes) that aren't compatible with previous versions. These changes establish a strong foundation for more extensive development in future releases.

In this release, we’ve made significant changes in our core architecture to increase security and performance. Before upgrading, visit the Jira 11.0 upgrade notes to review important upgrade steps and see the full list of issues resolved.

Check the compatibility of your Marketplace apps

As a major release, Jira 11.0 introduces backward-incompatible changes to the apps' API. If you build custom in-house apps, you need to test their compatibility and update them.

If you have installed apps from the Atlassian marketplace or another source, you also need to check their compatibility and update them before performing the upgrade. To check app compatibility, visit Checking app compatibility with application updates or the Atlassian Marketplace to see if your app hosting is compatible with your product version.


Resolved issues

See the full list of the issues we’ve resolved throughout the lifecycle of Jira Service Management 11.0.

Issues resolved in 11.0.0

Released on 13 August 2025

T Key Summary Status Security Level
Loading...
Refresh

Last modified on Aug 14, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.