Jira Core 9.12.x upgrade notes

Jira Core release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Here are some important notes on upgrading to Jira Core 9.12.x Long Term Support (LTS).

Upgrading from 8.x to 9.x triggers full Jira reindex that causes some downtime during the process. If you’re on 8.x now, make sure you’ve estimated the downtime and set the best time for the upgrade.

Learn more about how to handle full reindex and estimate downtime

Jira Core 9.12.x is the last release to support Server licenses

Jira Core 9.12 will be the last release available to download for Server, prior to the Server end of support date on February 15, 2024. All following releases will only support our Data Center offering. As Jira Core 9.12 are long-term support (LTS) releases, they will continue to receive security and bug fixes until the end of support date on Feb 15, 2024.

We recommend that you migrate to the Atlassian Cloud offering or upgrade to Data Center to remain secure and supported. If you're thinking of moving to Data Center, check our recommendations first.

Upgrade notes

Jira Core 9.12.x is a long-term support (LTS) release. Normally, we don’t introduce new features in LTS releases but rather consolidate the ones we’ve introduced since the last LTS release (Jira 9.4.0).

The summary has been divided into sections that group the changes by severity and type:

Breaking changes

Learn about what you need to keep an eye on to avoid outages or disruptions. The entries in this section are organized chronologically from newest to oldest.

Jira 9.11: The allowlist for outbound HTTP requests in Jira Automation is now enabled by default

Since the release of Jira Automation 9.0 (bundled with Jira 9.11), the global configuration setting Check all URLs against the Jira allowlist is enabled by default. This means that you can’t publish a rule if the URL you’re requesting isn’t on the allowlist. The setting also breaks existing rules if the configured URLs aren’t on the allowlist — if a rule fails to run, you’ll see an error in the audit log. You can fix broken rules by adding the URLs to the allowlist or disabling allowlist verification.

For more information about this change, check out the following resources:

Jira 9.11: The introduction of secret key masking changes the behavior of the Webhook URL field in Jira Automation


In Jira Automation 9.0 (bundled with Jira 9.11), the Webhook URL field that appears when you create a rule with the Send web request action is now a menu instead of a text field. Additionally, for a webhook URL to become available in the menu, you’ll need to add it as a secret key.

For more information about this change, check out the following resources:

Jira 9.11: Enabling support for Amazon S3 object storage might break some API classes


Some Jira APIs aren’t compatible with the Amazon S3 object storage method. This means that apps that still use those APIs may not function correctly. The APIs in question are:

  • com.atlassian.jira.config.util.AttachmentPathManager
  • com.atlassian.jira.util.AttachmentUtils

For more details, check out the Jira Core 9.11 upgrade notes.

Jira 9.10: New Apache Tomcat is incompatible with older versions of the New Relic agent

In Jira Core 9.10, we’ve upgraded Apache Tomcat to version 9.0.75, which isn’t compatible with versions of the New Relic agent earlier than 8.2.0. This incompatibility might cause issues when Jira is started in the browser. We recommend that you upgrade the New Relic agent to version 8.2.0.

For more details, check out:

Jira 9.5: Jira migrates to Log4j 2.x

We’ve upgraded Log4j to version 2.17.2. Since this is a breaking change, some effort may be required to ensure that any existing custom Log4j 1.x configurations are compatible with this release of Jira.

For more details, check out Jira Core 9.5 upgrade notes

Fixes introduced in this release

Jira Core 9.12 also introduces its own set of changes that fix known issues, boost performance, and improve the overall user experience.

Improved security of DVCS webhook requests

We’ve added support for secret tokens to ensure that Jira accepts webhook requests only from trusted source code repositories. From now on, Jira will automatically generate and set webhook secret tokens for all of your linked DVCS accounts.

After upgrading to Jira 9.12, Jira will start securing all your existing DVCS accounts with webhook secret tokens. You may experience a delay in the synchronization of repository data. The time to completion will depend on the number of repositories to process.

For more details, check out Configuring webhook security.

Improvements, fixes, and non-breaking changes

Get a glimpse of all the improvements, fixes, and non-breaking changes added to each release leading up to Jira 9.12. The table is divided into rows by release. Every row contains a link to the relevant upgrade notes where you can learn the details.



Upgrade notes


  • Jira Automation receives Look up issues and Create variable actions DATA CENTER
  • Project shortcuts can now be reordered
  • Store attachments more efficiently in the S3 object storage DATA CENTER
  • Updated layout in the table with custom field contexts
  • Improvements to the support zip creation process
  • More granular control over project permissions DATA CENTER
  • Boosting Jira’s resilience to database connectivity dropouts
  • Progress bar added to the Database Integrity Checker for tracking the status of checks
  • User session invalidation across the cluster without the system reboot
  • Added support for the AWS Secrets Manager
  • New infrastructure metrics for in-product diagnostics
  • Deprecation of the Jira mobile web interface

Jira Core 9.11 upgrade notes


  • Search for projects and issue types in custom field contexts
  • Get notified about Jira reindexing only when it’s really required DATA CENTER
  • Obfuscate the plain text password in server.xml for Tomcat DATA CENTER

Jira Core 9.10 upgrade notes


  • Show empty custom fields in the issue view Data Center
  • Store your avatars in Amazon S3 DATA CENTER
  • Microsoft Graph API integration for incoming mail DATA CENTER
  • New importSettings field to manage the Developers project role DATA CENTER

Jira Core 9.9 upgrade notes


  • Sticky comment footer
  • Auto-managed sprints DATA CENTER
  • New mail queue metrics for in-product diagnostics DATA CENTER
  • JMX blocklist deserialization filter DATA CENTER

Jira Core 9.8 upgrade notes


  • Take index snapshots with one click
  • Design and functionality enhancements for configuring custom field contexts

Jira Core 9.7 upgrade notes


  • Crowd membership changes batched during full and incremental directory syncs
  • The cache app API has been deprecated and hidden behind a dark feature flag

Jira Core 9.6 upgrade notes


  • Support for Java 17 added
  • The H2 database upgraded from 1.4.200 to 2.1.214
  • Changes to the in-product diagnostics (IPD) tool
  • Jira temporary directory cleaner introduced

Jira Core 9.5 upgrade notes

Changes to supported platforms

See what changes have been made to supported platforms since the last Jira LTS release:

New supported platforms

Jira has gained support for the following platforms:

  • PostgreSQL 15 (Jira 9.10)
  • Microsoft SQL Server 2022 (Jira 9.10)
  • Pgpool-II (Jira 9.10)
  • Version 2 of the H2 embedded database (Jira 9.5)
  • Java 17 (Jira 9.5)

End of support

Support for the following platforms has been permanently removed:

  • Microsoft SQL Server 2016 (Jira 9.7)
  • The Android 4.0 mobile browser (Jira 9.5)

Deprecated support

Support for the platforms on this list will be removed in a future release:

  • PostgreSQL 10 and 11 (Jira 9.9)
  • Oracle 12c R2 (Jira 9.9)
  • Java 8 (Jira 9.7)

For more details, check out Supported platforms.

Known issues

This section contains information about any issues that we’ve discovered in our testing. We’re constantly keeping an eye out and if we find anything, we’ll let you know right here.

Jira 9.11: The Install4J library throws an exception when running the Jira installer for Linux on Java 17

Java 17 has been supported since Jira Core 9.5.0. In Jira Core 9.11.0, we've started to bundle Java 17 with Jira binaries (both archives and installers) for Linux and Windows.

There is a known issue with the Install4J runtime library, in which the Linux installer running on Java 17 throws a method invocation exception. Since the traceback message doesn't have any functional impact on Jira applications, no manual intervention is required.

For more details, check out Install4J runtime library throws exception when running the Jira 9.11 installer on Linux .

Upgrade procedure

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

App developers

See Preparing for Jira 9.12 for any important changes regarding apps and integrations.

Last modified on Nov 29, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.