Jira Software 11.2.x release notes
We're pleased to present Jira Software 11.2.
Highlights
- Welcome OpenSearch in Jira Data Center
- New limit of 10,000 items on a board
- Optimize your instance with safeguards
- Optimize your custom fields
- One place to clean them all
- Strengthen sysadmin and OS access separation
- Protect your Jira nodes with JQL resilience
- Connect securely with OAuth 2.0 for app links
- Rate limiting now supports OAuth 2.0
- Deprecation of Browse Project properties in workflows
- Indexing and snapshots improved with OpenSearch
- Handle large tables with Cluster message cleaning service
- React 18 and Atlaskit upgrade in Jira 11.2
- Jira mobile plugin removal
- Changes to supported platforms
- App developers
- Upgrade procedure
- Resolved issues
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 Service Management 11.2 release notes.
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:
- Configure OpenSearch for Jira
- OpenSearch hardware recommendations for Jira
- Search API deprecations and upgrade guide for Jira 11
- Migrating FieldIndexers in Jira 11
- Migrating Lucene collectors to Search API in Jira 11
New limit of 10,000 items on a board
For: END USERS ADMINS
This limit applies only when you’re using OpenSearch. The default Lucene search platform isn’t affected, but you can also configure Lucene to enforce the same limit.
With the OpenSearch implementation in Jira, Scrum and Kanban boards can display up to 10,000 items. When a board is full, an admin needs to update the board filter to reduce the number of included issues. This update helps Jira scale for large enterprises, improves search performance, and prevents indexing bottlenecks.
To check the total number of issues on your board, go to Issues, then select Search for issues and apply your board’s filter. By default, you can view up to 10,000 issues. An admin can override this limit by setting the jira.search.platform.max.result.window property.
More about issue display limits on boards
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:
- In the upper-right corner of your Jira application, select Jira administration, and then select System.
- In the sidebar, find Instance Optimizer and select Overview.
- 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
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
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 |
|---|---|---|
Only Jira System administrator can manage JMX settings. |
| |
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 some subsets of dark features. |
|
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. |
|
Protect your 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.
Connect securely with OAuth 2.0 for app links
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
Deprecation of Browse Project properties in workflows
For: ADMINS
Starting in Jira 11.2.0, we're deprecating the jira.permission.browse.* workflow step properties. These properties are used to restrict issue visibility on certain workflow steps.
Alternatively, you can set the issue security levels and automation rules to control which users can access the issue based on their project role and the current issue status. Update your workflows to use the alternative functionality
To preview the Browse Project removal enforcement, you can enable the com.atlassian.jira.workflow.permission.browse.removal feature flag. Jira permission manager will ignore these Browse Project properties starting from version 12.0.0.
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
Jira Mobile plugin removal
In Jira 9.11, we've deprecated support for the Jira mobile web interface. Now, in Jira 11.2, we’re removing the Jira Mobile plugin in favor of the Jira Data Center mobile app for iOS and Android.
Supported platforms 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.
App developers
See Preparing for Jira 11.2 for any important changes regarding apps.
Upgrade steps
Upgrading from Jira version 10.x.x?
- 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, 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 Software 11.2.