Jira Release Notes

We're pleased to present Jira Software 11.1.

Highlights

• Find missing issues in Advanced Roadmaps for Jira
• 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

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.1 release notes.

Find missing issues in Advanced Roadmaps for Jira

For: END USERS ADMINS

We’re introducing the Find your issue feature to help you quickly understand why a specific issue isn’t visible in your Advanced Roadmaps for Jira dashboard. You can search for any issue by its key, and Jira will analyze your dashboard’s filters and settings to explain why the issue is missing. Diagnostics run in the background. Each request is handled separately, and rate limits help maintain consistent performance. To find missing issues:

• 1. From the Roadmap tab, go to Settings, then Configure, then select Find your issues.
• 1. In the search box, enter the issue key and select Search.

More about missing issues in Advanced Roadmaps

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.
• 1. Select Create service account.
• 1. Follow the prompts to configure your service account’s details, scopes, and resources, then generate your OAuth 2.0 credentials.
• 1. 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 Software 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

See Preparing for Jira 11.1 for any important changes regarding apps.

Upgrade procedure

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

Issues resolved in 11.1.0

Released on 24 September 2025

• Timeout message not displayed correctly when releasing a large amount of issues from a Kanban board
• Timeout errors can occur when completing sprints in Scrum boards
• JIRA Software JAVA API for Version 7 and above
• Epic name character limit exists in GH but not JIRA
• The multi-byte characters are garbled in the Time since chart and the Resolution time gadgets
• No Confluence page found with the given URL while linking confluence web page
• Confluence displays the warning "Application 'xxx' seems to be offline. Click here to relocate" for application links to Jira when the dark feature "public.access.disabled" is enabled in Jira 10.3.x
• Invalid use of RequestCache by thread: JIRA-Import-Thread
• Editor: Buttons not operable with a keyboard
• Editor: Non-descriptive link text
• Automation rules cannot be published when copying the "Customer Request Type" field from relevant sources in "clone issue" or "edit issue" actions

Spring and Jakarta upgrade

To maintain high security standards and keep dependencies supported and up to date, we’re upgrading Spring to the 6.x line, Jakarta to EE Platform 10, Apache Tomcat to 10.1 as well as other libraries that depend on Spring and Jakarta.

The Apache Tomcat upgrade also introduces changes under the Jakarta Servlet specification. If you rely on custom server settings or connectors, review the following before upgrading:

• Check custom server.xml configurations, especially any references to "javax.servlet" APIs. Tomcat 10.1 has migrated to the "jakarta.servlet" namespace.
• Verify that any connectors (HTTP, AJP, etc.) are still supported and properly configured in Tomcat 10.1.
• Confirm that any security or TLS/SSL settings are compatible with Tomcat 10.1’s default cryptographic protocols.

For detailed information on the changes introduced in Tomcat 10.1, consult the official Apache Tomcat documentation.

Upgrade to jQuery 3

We’ve upgraded jQuery from version 2 (with [email protected]) to version 3 (with [email protected]) to align on jQuery versions across all Data Center products. This means a significant jQuery version uplift for products containing older versions of jQuery that will make developing cross-product apps easier.

For more details, refer to the jQuery Core 1.9 upgrade guide and jQuery Core 3.0 upgrade guide.

Removal of deprecated components in AUI 10

We’re removing some outdated AUI 10 components with design and accessibility issues (Dropdown 1 and Toolbar 1) and updating internal dependencies to better support jQuery 3 and proactively address security issues.

End of support for LESS

To enhance the security and performance, we’re removing the ability to transform LESS to CSS at runtime, requiring LESS to be transpiled into CSS at compile time.

Global serialization filter

We’re implementing a global serialization filter that relies on a central blocklist for Java deserialization, Velocity, Struts, and XStream. This filter is designed to block specific classes and patterns that are recognized as vulnerable to Remote Code Execution (RCE) through publicly known gadget chains.

Add scopes to REST endpoints to use OAuth 2.0 2LO

We’ve introduced @ScopesAllowed to improve security and control over REST endpoints. Add the @ScopesAllowed annotation to your endpoints to make them accessible using an OAuth 2.0 Client Credentials token (2LO). For example, this annotation requires that the access token has the WRITE scope before providing access to this endpoint.

@POST
@ScopesAllowed(requiredScope = "WRITE")
public void createEntity(...) {}

OAuth 2.0 security improvements

We're implementing several important changes to our OAuth 2.0 authentication process to enhance security and efficiency.

• Enforced global maximum time on access tokens: Access tokens will now have a maximum validity period of 1 hour. This change is designed to improve security by ensuring tokens are refreshed more frequently. You can change the value by setting the atlassian.oauth2.provider.access.token.expiration.seconds system property.
• Maximum lifetime of client ID and secret: The lifetime of client IDs and secrets is now 90 days by default. However, you can adjust this setting to a maximum of 730 days. This change aims to encourage regular rotation of credentials. You can change the value by setting the atlassian.oauth2.provider.client.credentials.expiration.seconds system property.
• Rotation of client credentials: We recommend regularly rotating your client credentials, including both the client ID and secret, to improve security. Setting up a rotation policy helps reduce the risk if credentials are ever compromised.
• Revocation of rotated client credentials: Once client credentials (client ID and secret) are rotated, the previous credentials can be revoked. This ensures that only the most recent credentials remain active, reducing the risk of unauthorized access.
• Revocation of user's refresh tokens: We now provide the ability to revoke all refresh tokens associated with a specific user. Additionally, administrators have the authority to revoke all refresh tokens for users within the system. This capability allows for greater control over session management and security.
• Maximum number of refresh tokens: The maximum number of refresh tokens allowed per client ID and user is limited to 25. This limitation helps manage resource usage and ensures that token proliferation is kept in check. You can change the value by setting the atlassian.oauth2.provider.refresh.token.limit.per.client.user system property.

Basic authentication disabled by default

We’re disabling authentication with basic authentication by default. This is a first step towards the removal of basic authentication altogether as we develop and mature alternatives to support the remaining few use cases.

Updated Tomcat protocols

We’ve updated the protocols provided by Jira extending the Tomcat protocols with support for password encryption:

The APR/Native library and the APR/Native Connectors, including both AJP and HTTP, are deprecated in Tomcat 10 and will be removed starting from Tomcat 10.1.x. Specifically, the Http11AprProtocol (HTTP connector) and the AjpAprProtocol (AJP connector) are deprecated. Consequently, com.atlassian.secrets.tomcat.protocol.AjpAprProtocolWithPasswordEncryption and com.atlassian.secrets.tomcat.protocol.Http11AprProtocolWithPasswordEncryption are no longer supported in Jira 11.

Changes to supported platforms

See what changes have been made to supported platforms in this Jira release. For more details, check out Supported platforms.

End-of-support announcements

We’ve removed support for:

• JDK 17
• PostgreSQL 15
• PostgreSQL 14
• PostgreSQL 13
• PostgreSQL 12
• MySQL 8.0
• Oracle 18c
• MSSQL Server 2017

Added support

• JDK 21
• PostgreSQL 17
• MySQL 8.4 LTS

This version of Jira will only run on Java 21.

App developers

See Preparing for Jira 11.0 for any important changes regarding apps.

Upgrade procedure

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.

We're pleased to present Jira Software 11.0.

Highlights

• Introducing the Jira Data Center connector for Rovo
• Removal of the deprecated Text gadget
• End of support for the Original theme
• New look and feel for Advanced Roadmaps for Jira
• Changes to issue sources filter for unsaved issues in Advanced Roadmaps for Jira
• Strict permission handling in Advanced Roadmaps for Jira
• Changes to System Dashboard operations
• Sorting on TEXT entity property
• Upgrade from ProForma Lite to ProForma Full
• Advance notice: OpenSearch opt-in feature ready for early access
• View your repo health with Sync history
• New backend issue limit for Advanced Roadmaps for Jira
• App signing is now enabled by default for app installations
• Check indexing stats in JMX
• Faster user management
• Simplification of multipart handling in WebWork
• Removal of Trusted apps
• Before you upgrade to Jira 11.0

Introducing the Jira Data Center connector for Rovo

For: END USERS ADMINS The Jira Data Center connector facilitates Cloud-based AI capabilities without requiring a full migration to the Cloud and allows data synchronization from Jira Data Center to Rovo in Atlassian Cloud. With Rovo, you can centralize knowledge from various platforms, providing a unified view of search results from both Cloud and Data Center, as well as third-party tools like SharePoint and Slack. You can boost productivity with Rovo Chat’s AI-driven insights and personalized responses, all while maintaining your existing infrastructure. Coming soon: You’ll be able to also include Jira Service Management Data Center projects and issues in Rovo’s unified search and AI experiences. Rovo, including search, chat, and studio apps as well as agents, is available to customers with a Premium or Enterprise Cloud plan of Jira, Confluence, Jira Service Management, or Teamwork Collection. Contact our team for assistance with setting up a new plan. Already have access to Rovo? Connect Jira Data Center to Rovo

Removal of the deprecated Text gadget

For: END USERS ADMINS We’ve removed the Text gadget for dashboards that we deprecated in Jira 9.11 and replaced with the Rich Text gadget to improve security in Jira.

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.

New look and feel for Advanced Roadmaps for Jira

For: END USERS ADMINS In Jira 10.7, we introduced a new look and feel for Advanced Roadmaps for Jira. Now, in Jira 11, we’re removing the feature flag behind those changes, making the modernized UI the new standard. This change brings consistency in how you and your team view and manage projects. New to Advanced Roadmaps? Discover Advanced Roadmaps for Jira

Changes to issue sources filter for unsaved issues in Advanced Roadmaps for Jira

For: END USERS We’re updating how issue sources are attached to newly created issues in Advanced Roadmaps for Jira plans. Now, new issues won’t have any issue source attached until you save them to Jira. Previously, new issues were immediately linked to their issue sources, allowing filters to apply to both saved and unsaved issues.

Strict permission handling in Advanced Roadmaps for Jira

For: END USERS ADMINS We’re adding strict permission handling for Jira issue filters used as an issue source in Advanced Roadmaps for Jira. Now, if you don’t have permission to view an issue filter, and that filter is used as an issue source in a plan, you won’t see the issues from that filter in your plan. The new approach ensures that issue visibility in plans always respects Jira’s permission model, bringing consistency across Jira. To include new issues in your plans, make sure they’re saved in Jira and that you have access to the relevant filters.

Changes to System Dashboard operations

For: END USERS ADMINS We’ve aligned the System Dashboard interface to accurately reflect permissible actions and prevent confusion:

• On the Shared Dashboards page, we've removed the dropdown menu with options to delete or change System Dashboard’s ownership.
• On the Manage Dashboards page, we’ve removed the Edit and Delete options. Now, you can only copy System Dashboard. These changes apply exclusively to the System Dashboard.

Sorting on TEXT entity property

For: END USERS ADMINS We’ve removed support for sorting on TEXT entity properties. This also applies to existing TEXT entity properties.

Entity properties declared with more than one type

If the same entity property is declared more than one time, only the first declaration will be considered and the subsequent declarations will be ignored. Considering the index-document-configuration module below, only the STRING property will be created. You can confirm whether a property has been ignored by configuring a logging level of DEBUG for the com.atlassian.jira.search.issue.index.indexers.impl.IssuePropertyIndexExtractor package.

Upgrade from ProForma Lite to ProForma Full

For: ADMINS The ProForma Lite app is no longer supported or available to download from the Atlassian Marketplace. Instead, you can now try a 30-day free trial of the full ProForma app to explore all ProForma features and enjoy a better forms experience. If you currently use ProForma Lite, plan to upgrade to the full, paid version of the ProForma app or check out the trial first. ProForma Lite won’t receive updates, compatibility fixes, or support. It might also stop working if it becomes incompatible with future Jira updates. If you’re using Jira Service Management, you can access all ProForma features for free. Explore ProForma licensing details

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 [email protected] or via our customer support channel.

View your repo health with Sync history

For: ADMINS We're introducing Sync history in the Distributed Version Control System (DVCS) admin section, a new feature that provides a repository sync audit log at a glance. Previously, admins couldn't access essential information about past repo syncs, making it challenging to assess the health of the sync process and debug errors. Now, you can access a detailed list of repository syncs from the past seven days in the audit table, reducing the time you need to identify and isolate problem areas. The details include start and end time, sync status, failure reason, duration, and type of sync (soft or full). To check the sync history of your repo:

1. Go to Settings, then Applications.
2. Go to DVCS accounts and open your account.
3. Next to the repo you want to check, select Show sync history.

New backend issue limit for Advanced Roadmaps for Jira

For: ADMINS We’ve increased the backend limit of issues that Jira can return in Advanced Roadmaps to 10,000. This change helps keep performance stable and ensures safe operation when working with large volumes of issue data in your plans. The frontend limit is still 5,000 issues.

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

Faster user management

For: ADMINS We've optimized the User Management view to reduce memory consumption and improve performance. Now, instead of navigating through all pages, the default display is limited to 10,000 users or 500 pages, which significantly reduces rendering time. To adjust this limit, go to System, select Advanced settings, and change the value of the jira.user.management.browsable.results.limit property. More about managing users

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 Software 11.0.

Issues resolved in 11.0.0

Released on 13 August 2025 [Detailed list of resolved issues omitted for brevity]

Issues resolved in 11.0.1

Released on 4 September 2025 [Detailed list of resolved issues omitted for brevity]

Last modified on Sep 4, 2025 Was this helpful? Yes No Provide feedback about this article Powered by Confluence and Scroll Viewport.

We're pleased to present Jira Software 10.7.

Highlights

• New look and feel for Advanced Roadmaps for Jira
• Dates now follow profile timezone in Jira automation
• Improve Jira performance with Instance optimizer
• Redirect email replies for Jira notifications
• View your repo health with Sync history
• Feature flags removal
• New entry in deserialization blocklist
• Resolved issues

Due to an issue, we’ve removed the ability to download Jira Software Data Center 10.7.0. Jira Software Data Center 10.7.1 provides a fix for this issue.

Read the upgrade notes for important info about this release and see the full list of issues resolved.

Compatible applications

If you're looking for compatible Jira applications, look no further: Jira Service Management 10.7 release notes.

New look and feel for Advanced Roadmaps for Jira

For: END USERS ADMINS

We're rolling out major updates to the user interface in the Advanced Roadmaps for Jira. These enhancements provide a seamless experience across Programs and Plans, ensuring consistency in how you view and manage your projects.

Here’s what's new:

• Restructured user interface and improved administration and program management functionalities for a more intuitive experience.
• Implemented dark theme, offering a modern and visually appealing interface. To test your apps for compatibility, enable the dark theme by going to your Profile, then Theme, and select Dark.

With these changes, we've also addressed security and accessibility concerns and reduced technical debt by updating outdated technologies.

Dates now follow profile timezone in Jira automation

For: END USERS ADMINS

We're updating how dates and times are displayed in Jira automation. Now, they'll be displayed in the timezone set in your Profile settings. Previously, these were shown in your system timezone. The timezone information will also appear alongside the dates and times. This change affects the following screens:

• Audit logs
• Performance insights
• Rule details

Improve Jira performance with Instance optimizer

For: ADMINS

We're introducing a new, more efficient way to manage Jira performance. Meet Instance Optimizer for Jira—a Marketplace app designed to help you identify and fix performance issues on your Data Center instance.

Instance optimizer contains key automation features and recommended settings that ensure your Jira stays fast and stable:

• 1. Index auto-healing automatically detects and resolves indexing issues, ensuring your app’s performance remains optimal without requiring full reindexing.
• 1. Database integrity checks functionality regularly scans and fixes inconsistencies in Jira’s database.
• 1. Custom fields optimization is now part of the optimization features, so you can clean up your fields and proactively improve performance in one place.

Redirect email replies for Jira notifications

For: ADMINS

We're introducing a feature that lets you set the Reply-to header in email notifications. This ensures that replies are directed to a different address than the From address, preventing mismatches and protecting sensitive information.

The new field in Jira is called Receive replies at and you can find it on the following screens:

• Outgoing mail form in Settings, then System, then Outgoing mail, and open Configure new SMTP Mail Server
• Outgoing mail overview in Settings, then System, then Outgoing mail
• Project summary page in Settings, then Projects
• Project notifications page in Settings, then Projects
• Jira Setup Wizard in Select project and Summary

View your repo health with Sync history

For: ADMINS

We're introducing Sync history in the Distributed Version Control System (DVCS) admin section, a new feature that provides a repository sync audit log at a glance. Previously, admins couldn't access essential information about past repo syncs, making it challenging to assess the health of the sync process and debug errors.

Now, you can access a detailed list of repository syncs from the past seven days in the audit table, reducing the time you need to identify and isolate problem areas. The details include start and end time, sync status, failure reason, duration, and type of sync (soft or full).

To check the sync history of your repo:

• 1. Go to Settings, then Applications.
• 1. Go to DVCS accounts and open your account.
• 1. Next to the repo you want to check, select Show sync history.

Feature flags removal

For: ADMINS

We’ve removed two feature flags:

• com.atlassian.jira.agile.darkfeature.boards.find.on.board.sprint.optimized.disabled - the legacy solution that was already turned off by default has now been removed. Only the optimized solution works now.
• com.atlassian.jira.agile.darkfeature.legacy.epic.picker - the legacy solution was disabled by default in Jira 8.20.5. We’ve now removed it and only left the optimized solution.

New entry in deserialization blocklist

For: ADMINS

We’ve added a new entry to the list of classes that are blocked from deserialization: org.springframework.transaction.jta.JtaTransactionManager.

This update enhances security by preventing remote code execution (RCE) attacks via Java Management Extensions (JMX) when the JtaTransactionManager is sent as a payload.

Resolved issues

See the full list of the issues we’ve resolved throughout the lifecycle of Jira Software 10.7.

Here are some important notes on upgrading to Jira Software 10.7.x. For details of the new features and improvements in this release, see the Jira Software 10.7 release notes.

New webhook URL encoding behavior

We’ve updated the way webhook URLs are encoded. Before, Jira would decode and re-encode special characters with varying rules for different characters, leading to inconsistent handling of webhook URLs. For example:

• %3D and = would both end up as =
• %25 and % would both get encoded as %25 Now, Jira no longer modifies URLs. For example:
• %3D in a URL will stay as %3D
• = will stay as =. If you’ve applied custom workarounds like double-encoding of some characters, you'll need to remove them after upgrading to Jira 10.7.0.

Changes to supported platforms

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

App developers

See Preparing for Jira 10.7 for any important changes regarding apps.

Upgrade procedure

Upgrading from Jira version 9.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.

Here are some important notes on upgrading to Jira Software 10.0.x. For details of the new features and improvements in this release, see the Jira Software 10.0 release notes.

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.

To increase security and performance, we’ve made changes in our core architecture that require apps to bundle their libraries. We’re collaborating with our Marketplace partners on these changes, however, some apps may not be immediately compatible with the new platform upon release and cause product experience breaks. We recommend that you review your apps before upgrading to avoid service disruptions for your organization.

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.

Async webhooks are now default in Jira Data Center

Starting from Jira Data Center 10.0.0, asynchronous webhooks are now the default and only option. This update significantly improves the user experience by processing webhooks through a dedicated thread pool, rather than tying them to the user request. Previously, in Jira 9 and earlier, webhooks were processed synchronously, with the most computationally intensive work performed during the HTTP request.

Environments with exceptional webhook usage in both Jira 9 and 10 might exceed the guardrails set by the default parameters. We recommend testing the asynchronous webhooks within your staging environments before a final upgrade. If you experience any issues, check our list of known problems or reach out to our support team.

Explore how to tune webhook performance parameters in Jira

Automation for Jira compatibility check

During the Jira update check, the Automation for Jira app will be flagged as Incompatible. You can safely ignore this warning. The app will continue functioning properly after upgrading Jira, and no additional actions are needed. For more information, refer to the knowledge base article.

Front-end API changes

This release brings an improved and updated Code sharing section of the Jira Data Center front-end API. We’ve introduced the following changes:

• Inclusion of Jira-specific API modules, such as requested Jira Events.
• Extensions and updates to common libraries.
• Introduction to particular versioning of common libraries and alias module type.
• Annotations to modules on the UPM level and better descriptions in the code.

Regular modules for the common libraries are versioned up to the minor version (x.y), for example, under the jira-frontend-api:react-18.3 web-resource Jira provides React 18.3.1, as of now. The patch version (aka bug fix) can be changed at any time, for example, the same web-resource can provide React 18.3.2 in the future.

The alias modules are versioned up to the major version (x), for example, under the jira-frontend-api:react-18 web-resource Jira provides React 18.3.1, as of now. The minor version can be changed at any time, for example, the same web-resource can provide React 18.4.0 in the future.

See the full list of changes

OpenAPI standard for REST API documentation

REST API documentation for Jira Core and Jira Software is now available in an OpenAPI standard with a refreshed graphical form. This is the first time REST API documentation for Jira Core and Jira Software is no longer split. What’s more, we’ve reviewed and updated the documentation content.

Get started with REST API documentation for Jira

Removal of previously deprecated feature flags

In this release, we’ve removed the following feature flags:

• com.atlassian.jira.agile.darkfeature.burnupchart
• optimistic.transitions
• com.atlassian.jira.advanced.audit.log
• velocity.chart.ui
• jira.quick.search
• com.atlassian.jira.custom.csv.escaper
• atlassian.cdn.static.assets
• jira.users.and.roles.page.in.react

All features previously hidden behind those feature flags were enabled by default.

Breaking changes to the Java API

In this release, we've removed several deprecated methods and classes. Additionally, we’ve made adjustments to a group of methods which involved modifying the signatures and return types.

Here’s what’s been changed:

• Removed or replaced various classes and methods with instructions for alternatives or replacements.

Breaking changes to the REST API

In this release, we’ve removed a set of REST API endpoints that have been deprecated since Jira Software 9.x.

Removal of dependencies

In this release, we’ve removed access to a number of dependencies.

Removal of binary installers

Starting from Jira 10.0, the .bin and .exe installers will no longer be available. You can still install Jira using the .zip and .tar.gz distributions.

Because of this change, Java is no longer bundled with Jira.

Jira Software and Jira Core dialogs migrated to AUI Dialog 2

This is still a work in progress. You can expect to see the full removal of AUI Dialog 1 from the Jira codebase by the upcoming LTS release.

Jira Software and Jira Core currently stand with significant majority of the components migrated to use AUI Dialog 2. AUI Dialog 1 will be removed from Jira completely by the upcoming LTS release. If your app uses that component, make sure to migrate to AUI Dialog 2.

Application Links compatibility

Starting from Jira 10.0, Application Links are only backward-compatible with products that have integrated a particular bug fix addressing incorrect Application Links version parsing. To enable Application Links to function properly, make sure to upgrade any other Atlassian products to a minimum supported version.

Known issues

• Redirect behavior of Stronger Defaults: Requests are redirected (HTTP 302) to the login page when a security clearance requirement isn't met, except for REST endpoints which are rejected (HTTP 401/403). Code calling non-REST endpoints must handle redirection.
• Automation for Jira 9.0.1 upgrade: Issues with automation rules when upgrading from Jira 8.20.x or later to Jira 10.0. Manual SQL script execution may be required.
• Important notice for MSSQL users: Jira 10.0.1 has a known issue preventing startup due to a change in the default encrypt parameter in the MSSQL JDBC driver. The issue is fixed in Jira 10.1.1; skipping 10.0.1 is recommended.

Upgrade procedure

Before upgrading, check app compatibility by visiting Checking app compatibility with application updates or the Atlassian Marketplace to see if your app hosting is compatible with your product version.

For upgrading from Jira version 9.x.x, see Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps. For a more tailored upgrade, use Jira administration > Applications > Plan your upgrade for a custom upgrade guide with step-by-step instructions.

Last modified on May 15, 2025

Highlights

• Async webhooks are now default in Jira Data Center
• New database integrity check for validating issue links
• New API endpoint for reciprocal issue links
• Remove deleted users marked as inactive
• Resolved issues

More

Read the upgrade notes for important info about this release and see the full list of issues resolved.

Compatible applications

If you're looking for compatible Jira applications, look no further: Jira Service Management 10.6 release notes.

Async webhooks are now default in Jira Data Center

For: ADMINS

Starting from Jira Data Center 10.0.0, asynchronous webhooks are now the default and only option. This update significantly improves the user experience by processing webhooks through a dedicated thread pool, rather than tying them to the user request. Previously, in Jira 9 and earlier, webhooks were processed synchronously, with the most computationally intensive work performed during the HTTP request.

Environments with exceptional webhook usage in both Jira 9 and 10 might exceed the guardrails set by the default parameters. You can customize these limits to better suit your organization’s needs. We recommend testing the asynchronous webhooks within your staging environments before a final upgrade. If you experience any issues, check our list of known problems or reach out to our support team.

Explore how to tune webhook performance parameters in Jira

New database integrity check for validating issue links

For: ADMINS

We've added a new database integrity check to ensure that all issue links in Jira are associated with valid issue link types.

This change addresses a common problem when issue link types are deleted from the database but remain in the user interface, causing errors during reindexing. The new integrity check detects and deletes such links from the database, ensuring an uninterrupted reindexing process.

Learn more about database integrity checks

New API endpoint for reciprocal issue links

For: END USERS ADMINS

We're introducing a new REST API endpoint that makes it easier to create reciprocal issue links between different Jira instances. Previously, you needed to send two separate REST requests to achieve this. Now, with the following endpoint, you can establish these links with a single request.

(POST) {source_jira_url}/rest/api/2/issue/remotelink/reciprocal

This endpoint accepts a JSON payload specifying the source and target Jira instances, along with the necessary details for the link.

Explore Jira Data Center REST API documentation

Remove deleted users marked as inactive

For: ADMINS

You can now manually remove externally deleted users marked as inactive directly from the user management view.

Learn how to remove a user

This feature is on by default. To turn it off, disable the com.atlassian.jira.user.allowDeleteExternallyDeletedUsers feature flag.

Resolved issues

See the full list of the issues we’ve resolved throughout the lifecycle of Jira Software 10.6.

Issues resolved in 10.6.0

Released on 23 April 2025

[Detailed list of resolved issues omitted for brevity]

Issues resolved in 10.6.1

Released on 20 May 2025

[Detailed list of resolved issues omitted for brevity]

Last modified on Jun 5, 2025

Was this helpful?

Yes

No

Provide feedback about this article

Changes to supported platforms

See what changes have been made to supported platforms in this Jira release. For more details, check out Supported platforms.

Added support

In Jira 10.6, we’ve added support for:

• MySQL 8.4
• Oracle 23ai
• PostgreSQL 16
• Java 21 runtime level

End-of-support announcements

In Jira 10.6, we’ve deprecated:

• PostgreSQL 15
• JDK 17
• MySQL 8.0
• MSSQL Server 2017

In Jira 11, we’ll remove support for:

• JDK 17
• PostgreSQL 15
• PostgreSQL 14
• PostgreSQL 13
• PostgreSQL 12
• MySQL 8.0
• Oracle 18c
• MSSQL Server 2017

App developers

See Preparing for Jira 10.6 for any important changes regarding apps.

Upgrade procedure

Upgrading from Jira version 9.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.