Jira Service Management 11.3.x release notes
3 December 2025
We're excited to present Jira Service Management 11.3.
Highlights
More
See the full list of issues resolved.
Compatible applications
If you're looking for compatible Jira applications, look no further:
Jira Service Management 11.3 is a Long Term Support release
This means we'll provide bug-fix releases until 11.3 reaches end of life, to address critical security, stability, data integrity, and performance issues. See our bug fix and security bug fix policies for more information.
What's changed since the last LTS release
A lot has changed since we released Jira Service Management 5.12 and Jira Software 9.12, which were the last Long Term Support releases. Have a look at our change logs to get a quick roll-up of the most important changes.
Improvements introduced in this release
Assets date format changes
Following the Jira date picker format changes, we have identified and fixed issues with date handling in Jira Service Management Assets for datetimes.
We introduced fixes to Unix Epoch date time parsing via Assets import for second, millisecond, and microsecond precision.
This update provides a fix for a bug which caused datetimes parsed with WindowsNT to always be shown with year 20xx.
With these changes, you can expect the following:
- Due to format ambiguity, we do not support assets import of Unix Epoch date times with nanosecond precision. 18-digit integers greater than 111,000,000,000,000,000 continue to be parsed with the WindowsNT datetime parser and may result in incorrect date being shown.
- Existing datetimes that have been incorrectly parsed with WindowsNT datetime parser may still show an incorrect date with year
20xx.This may mask historic datetime parsing issues.
Important updates introduced in Jira 11.2
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.
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
Performance reports
We run extensive performance tests to compare our Long Term Support releases to see how the new features affect Jira, and to make sure we’re not introducing any performance regressions. LTS releases are usually a few versions apart, so the improvements in performance are much more visible than between smaller, feature releases.
Supported platform changes
See what changes have been made to supported platforms since the last Jira LTS release:
End of support
We've removed support for:
- JDK 17
- PostgreSQL 12
- PostgreSQL 13
- PostgreSQL 14
- PostgreSQL 15
- MSSQL Server 2017
- MySQL 8.0
- Oracle 18c
Deprecated support
We’ve deprecated support for:
- PostgreSQL 16
- MSSQL Server 2019
- Oracle 19c
Confirmed support
We’ve confirmed support for:
- JDK 21
- MySQL 8.4
- Oracle 23ai
- PostgreSQL 17
This version of Jira runs only on Java 21.
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.3 for any important changes regarding apps.
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
Issues resolved in 11.3.0
Released on 3 December 2025
Issues resolved in 11.3.1
Released on 19 December 2025
Jira Service Management 11.3.x Long Term Support release change log
§Jira Service Management 11.3 is a Long Term Support release, and this change log gives you an overview of what's changed in earlier versions.
About Long Term Support releases 
We recommend upgrading Jira Service Management regularly. However, if your organization's process means you only upgrade about once a year, upgrading to a Long Term Support release may be a good option, as it provides continued access to critical security, stability, data integrity, and performance issues until this version reaches end of life.
Jira Service Management 11.3.x Long Term Support release performance report
About Long Term Support releases
We recommend upgrading Jira Service Management regularly. However, if your organization's process means you only upgrade about once a year, upgrading to a Long Term Support release may be a good option, as it provides continued access to critical security, stability, data integrity, and performance issues until this version reaches end of life.