Jira Service Management 11.2.x release notes

Jira Service Management Release Notes

On this page

In this section

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

6 November 2025

We're excited to present Jira Service Management 11.2.

Highlights

eDecorative image of the download section

Get the latest version

Compatible applications

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

More

See the full list of issues resolved in this release.

Farewell Opsgenie

For: ADMINS AGENTS

On April 5, 2027, Opsgenie will no longer be supported or accessible. We recommend planning your migration to avoid disruption to your incident management processes.

As part of our cloud-first strategy, we’re bringing Opsgenie’s alerting and on-call capabilities into the Atlassian platform. Since Opsgenie is a cloud-only product, Data Center customers need to migrate to Jira Service Management Cloud or Compass before April 5, 2027 to keep these features.

To see recommended migration options for your Opsgenie sites, go to Settings, then select Migrate Opsgenie.

To maintain continuous incident management coverage, choose one of these migration paths before support ends:

  • Move Jira Service Management Data Center to Cloud, then migrate Opsgenie.

  • Migrate your Opsgenie instance to a new Jira Service Management Cloud site.

  • Migrate your Opsgenie instance to a new Compass site.

You’ll have full access to Opsgenie until April 5, 2027. If you don’t migrate by then, you can still download your Opsgenie data, but you’ll lose access to incident management features.

Read more about migrating to cloud or contact us.

For: ADMINS

You can now connect your Jira Service Management to the Confluence knowledge base, Assets Confluence attributes, and Assets-Confluence macro through OAuth 2.0. With OAuth 2.0, impersonation is automatic, and Jira will act as the logged-in user when making requests to Confluence.

To configure the integration, select the JSM_KB scope and set the Confluence incoming link to READ. The integration is compatible starting from the following versions:

  • Jira Service Management Data Center 11.0

  • Confluence Data Center 10.0

  • Assets-Confluence macro 3.0.0

If your Jira and Confluence instances don't share the same userbase, avoid using OAuth 2.0, as impersonation relies on matching usernames. OAuth 1.0 connections will continue to work, but you must manually recreate the application link to switch to OAuth 2.0.

More about linking Jira to Confluence

New REST API scopes for service accounts

For: ADMINS

We’ve added support for service accounts in Jira Service Management and Assets by introducing READ and WRITE scopes to public REST API endpoints. This update lets you control access for service accounts, so you can specify whether an integration or automation can read or write data through the API:

  • Use READ for retrieving data.

  • Use WRITE for making changes.

In this release, we’ve added the ScopesAllowed annotation. This change is part of our ongoing service accounts project for Data Center. Join the Early Access Program for service accounts

Decorative image of the divider

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

Welcome OpenSearch in Jira Data Center

For: END USERS ADMINS

OpenSearch is now fully supported for production use. You can configure Jira to use OpenSearch as your search platform, either on premises or as a managed service like AWS OpenSearch Service. We recommend switching to OpenSearch because it offers performance, scalability, and reliability improvements over Lucene.

OpenSearch in Jira isn’t just about searching — it supports everything you do, from loading boards and viewing backlogs to generating reports and working with issues. Because so many core actions rely on search, OpenSearch’s speed, consistency, and reliability have a direct impact on your team’s productivity and experience. By using OpenSearch instead of Lucene, you’ll be able to speed up you Jira, reduce the number of required Jira nodes, and use cheaper hardware.

To understand the differences between OpenSearch and the default Lucene search platform, review the OpenSearch for Jira Data Center guide. 

You might also want to get familiar with our previous OpenSearch documentation:

Optimize your instance with safeguards

For: ADMINS

Jira Instance Optimiser now includes safeguards to help you stay within recommended limits for comments, custom fields, issue types, issues, and projects. These safeguards help maintain system stability and performance as your instance grows.

To set up the limits:

  1. In the upper-right corner of your Jira application, select Jira administration, and then select System.
  2. In the sidebar, find Instance Optimizer and select Overview.
  3. Select Configure safeguards.

You can enable or disable safeguard enforcement, and choose whether to receive email and in-app notifications. When usage approaches a set limit, system admins receive notifications. If a user tries to perform an action that would breach a safeguard, the action is blocked and the user receives a warning. Explore how to configure safeguards in Instance optimizer

Image of safeguards in Instance optimizer

Optimize your custom fields

For: ADMINS

Instance optimizer now makes it easier to manage your custom fields. You can search, filter, and take bulk actions, including deleting custom fields directly from the recommendations page. You can also see more details about custom field usage and the impact of localizing these fields.

You can scan your custom fields to identify those with configurations that can be optimized. If your last scan is more than 24 hours old, you will need to re-scan to ensure you have the most up-to-date data. After 24 hours, previous scan results are no longer displayed.

Optimize your custom fields in Jira

Image of custom fields optimization in Instance optimizer

One place to clean them all 

For: ADMINS

We're deprecating the Clean up functionality in Jira Data Center and removing the Audit Custom Fields link. Instead, the cleanup features, such as project and issue archiving, are now integrated into the preinstalled Instance Optimizer app, which provides more efficient and automated ways to optimize your instance.

With this change, you’ll find all the cleanup features in one place. More about Instance Optimizer for Jira

Strengthen sysadmin and OS access separation

For: ADMINS

Starting from Jira 11.2, we’ve clarified the distinction between the global administrative permissions: Jira administrator and Jira System administrator and introduced new application properties. You can use them to ensure that only users with the highest level of administrative access can perform sensitive operations.

In Jira 11.2, the stricter permissions are opt-in, but they'll become opt-out in a future major version of Jira Data Center.

System administrators can update these properties in the advanced settings in Jira. By default, they’re set to false and let you opt in to the updated role requirements at your own pace. You can test them by setting the property value to true. Enable each property individually to apply stricter permissions

Feature

New permission

Property

Changing Java Management Extensions (JMX) settings.

Only Jira System administrator can manage JMX settings.

jira.jmx.strict.admin.permission

Enabling or disabling certain dark features that impact security, infrastructure, core configuration, or expose sensitive system-level data.

Only Jira System Administrator role can manage dark features.

jira.feature.flags.strict.admin.permissions

Loading recovery indexes from Jira home directory.

Currently, it's possible to load recovery indexes from an absolute path, including locations on the local file system. To align with the approach used for backup and restore, you can require that recovery indexes are loaded only from the Jira home directory.

Only allow loading an index from a path relative to Jira home.


jira.index.recovery.from.relative.path.only

More about global permissions

Protect you Jira nodes with JQL resilience

For: ADMINS

We’re introducing JQL resilience, a set of safeguards that help prevent node crashes caused by resource-intensive JQL operations. To stop a JQL query from using too much memory or running for too long, you can:

  • set a maximum search result limit.
  • define a JQL query time limit to interrupt queries that run too long.
  • enable a memory usage circuit breaker to reject new JQL queries when memory is low.

For each node, you can control these limits in the jira-config.properties file. Each change requires you to restart Jira for it to take effect. Explore how to use JQL resilience

When these features are enabled, some JQL searches might return a SearchException in situations you didn’t encounter before, such as timeouts. Jira logs these events and publishes them in the audit log. Use these features only when the risk of node crashes outweighs the impact of failed queries.


For: ADMINS

We’ve added OAuth 2.0 support for application links (app links) across Atlassian Data Center products. OAuth 2.0 is an industry-standard authentication protocol that enables secure mand reliable connections between Atlassian products and external applications. More about creating applinks

We’re also working on OAuth 2.0-based app links to connect with cloud to allow for secure and efficient integrations of hybrid environments, and will share the timeline soon.

Rate limiting now supports OAuth 2.0

For: ADMINS

Rate limiting in Jira now supports OAuth 2.0 2-legged (2LO) authentication. This update lets you configure rate limits for OAuth 2.0 requests separately from other API requests, making it easier to manage integrations like the Rovo connector.

More about rate limiting in Jira

Indexing and snapshots improved with OpenSearch

For: ADMINS

When OpenSearch is enabled in Jira Data Center, you’ll notice changes to both the user interface and REST APIs. The Index Admin UI now uses a new URL (OpenSearchIndexAdmin.jspa) and offers a different set of configuration options tailored for OpenSearch.

The indexing and snapshot API endpoints now reflect OpenSearch-specific behavior.

  • The reindex endpoint always performs a full background reindex:
    • /jira/rest/api/2/reindex
  • The snapshot endpoints are disabled because they don’t apply to OpenSearch:
    • /rest/api/2/index-snapshot
    • /rest/api/2/cluster/index-snapshot/{nodeId}

Handle large tables with Cluster message cleaning service

For: ADMINS

The Cluster message cleaning service now deletes expired rows in batches of 100,000, making it easier to manage very large tables, even up to 100 million rows. This update prevents database strain by avoiding single, large transactions that could cause memory or disk issues.

Configure Cluster message cleaning service in Jira

React 18 and Atlaskit upgrade in Jira 11.2

For: ADMINS

In Jira 11.1, we upgraded React to version 18 and updated Atlaskit components to their latest versions for Platform packages, Jira Service Management, and Assets. In Jira 11.2, these upgrades have now been applied across the rest of Jira. This change reduces vulnerabilities inherited from older Atlaskit packages and brings recent bug fixes and accessibility improvements to Jira.

As part of this update, some React web resources have been deprecated. If your custom apps or integrations rely on these resources, check out the recommended replacements for improved performance. More about Web Resource deprecation and replacements

decorative image of the supported platforms section Supported platform changes

In Jira 11.2, support for Microsoft SQL Server 2019 (MSSQL 2019) is deprecated.

For the list of supported platforms, see Supported platforms.

For previous announcements, see End of support announcements.

decorative image of the app developers section App developers

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

Decorative image of the upgrade procedure section Upgrade steps

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.2.

Issues resolved in 11.2.0

Released on 6 November 2025

T Key Summary Status Security Level
Refresh

Last modified on Nov 24, 2025

Was this helpful?

Yes
No
Provide feedback about this article

In this section

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.