Jira Service Management 11.1.x release notes

24 September 2025

We're excited to present Jira Service Management 11.1.

Highlights

• Faster scrolling on the customer page
• UI updates in Assets
• Access workload data without wait
• Lucene removed from canned responses
• Indexing in Assets is now simpler
• Limit object traversal in Assets
• Manage your integrations and automations with service accounts
• Sign SAML authentication requests
• React 18.3 and Atlaskit upgrade
• Changes to supported platforms
• App developers
• Upgrade procedure
• Resolved issues

e

Get the latest version

More

See the full list of issues resolved in this release.

Compatible applications

If you're looking for compatible Jira applications, look no further: Jira Software 11.1.x release notes.

Faster scrolling on the customer page

For: EVERYONE

The customer page now loads much faster, thanks to a new scroll-based pagination experience. Previously, this page could take several minutes to display all customers, especially in large instances. With this update, you can quickly browse customers as you scroll, without waiting for the entire list to load.

No functionality has been removed — page state wasn’t stored in the URL before, so the workflow remains unchanged.

UI updates in Assets

For: EVERYONE

As part of ongoing UI component improvements, we’re introducing a series of updates to Assets UI. These changes don’t affect functionality and are focused on usability and accessibility improvements.

We’re updating the following areas:

• Share these results modal for Assets searches

• Edit color theme pop-up

• Upload icon window

• screens for creating and editing objects

• DateTime field

• Assets details view and banner layout

• comments

• Attachments and Comments buttons

• Print QR Code pop-up

• Delete confirmation pop-up

• References tab

• Add attachment dialog

• Print label modal

• search view

• bulk action messages

• Report Manager view

• reports share options

• modals on the Asset Details Template/Layout configuration page

Access workload data without wait

For: AGENTS ADMINS

We’ve boosted the performance of the Workload report page, so you no longer have to sit through long load times in large environments. The main page now appears right away, while the Issues in progress bar loads just after. You’ll get to your insights faster, even in the busiest projects.

Not sure how to use reports? Track your team's success with reports

Lucene removed from canned responses

For: AGENTS ADMINS

We're removing the Lucene dependency from canned responses to improve performance, especially as the number of canned responses increases in larger instances.

With this change, searches for canned responses now match titles and content directly in the database. Lucene’s relevance scoring is no longer available, but results are still sorted by usage and last updated date.

The new database search is enabled by default with the feature flag sd.canned.responses.search.sql.disabled. Admins can disable this feature flag to revert to Lucene indexing. Keep in mind that Lucene indexes might be outdated, so you’ll need to restart your instance, perform a full reindex, or reindex canned responses using the following API endpoint: /rest/servicedesk/canned-responses/1/index/reindex-all.

Explore canned responses

Indexing in Assets is now simpler

For: ADMINS

We've simplified the indexing process in Assets to improve reliability and reduce complexity. Now, all Assets indexes (except for the free text index) are always rebuilt directly from the database at startup. This makes your index always consistent with your data.

We’ve removed the options to store the cache on shutdown or restore the index from a file. This change makes the process more straightforward and reduces the risk of using outdated or corrupted index files. Previously, admins could manually persist the Assets index to disk and restore it on startup.

You’ll still benefit from fast in-memory indexing and improved performance for Assets queries. More about indexing Assets

Limit object traversal in Assets

For: ADMINS

We've introduced a limit on the number of Assets objects that can be traversed (visited through object reference attributes) in a single request. This limit helps prevent Jira from running out of memory and crashing.

By default, the traversal limit is 100,000 objects. A request that traverses this many objects is expected to use about 500MB of memory. You can adjust the limit on the Assets configuration page in the admin settings. To disable traversing entirely, set the limit to 0. However, disabling the limit may expose your instance to out-of-memory errors.

This update applies to the /rest/insight/1.0/iql/objects and /rest/insight/1.0/aql/objects endpoints.

More about configuring global Jira settings for Assets

Manage your integrations and automations with service accounts

 For:  ADMINS

Service accounts are specialized, non-user accounts created for secure and efficient management of automated processes and external integrations. With service accounts, you can securely access REST APIs using the OAuth 2.0 authentication method to execute scripts and run tasks while maintaining full control of permissions. All actions performed by service accounts are tracked, providing visibility into their operations.

To set up a service account:

1. Go to Administration, then User management, then from the sidebar select Service accounts.
2. Select Create service account.
3. Follow the prompts to configure your service account’s details, scopes, and resources, then generate your OAuth 2.0 credentials.
4. Review all the details and copy your credentials to a safe place.

Explore how to manage a service account

Sign SAML authentication requests

For:  ADMINS

We’re implementing signed Security Assertion Markup Language (SAML) authentication requests to strengthen your instance’s security. When SAML is enabled, the authentication plugin generates a certificate and private key during startup. The private key signs SAML authentication requests, and you can download the certificate to upload to your Identity Provider (IdP). This lets the IdP verify the authenticity and integrity of each request.

To enable signing SAML authentication requests, go to the Authentication methods page and select Sign requests. Explore SAML single sign-on for Atlassian Data Center applications 

React 18.3 and Atlaskit upgrade

For:  ADMINS

We're upgrading Jira Data Center to use React 18.3 and the latest Atlaskit components. This update helps keep your instance secure and compliant by enabling continuous security updates and bug fixes from Atlaskit and React. In Jira 11.1, we upgrade Platform packages, Jira Service Management, and Assets.

The React 16 web resources exposed by Jira are now deprecated. We recommend migrating your custom apps and integrations to React 18.3 to ensure compatibility and continued support. Review code sharing and migration guidance

Changes to supported platforms

This release of Jira Service Management doesn’t introduce any changes to supported platforms.

For the list of supported platforms, see Supported platforms.

For previous announcements, see End of support announcements.

App developers

Check out Preparing for Jira 11.1 for any important changes regarding apps.

Upgrade procedure

To help you upgrade to the latest and greatest:

• See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps.

• For a more tailored upgrade, go to Jira administration, then Applications, and then Plan your upgrade. We’ll recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.

Resolved issues

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