Jira Core 8.18.x upgrade notes
Here are some important notes on upgrading to Jira Core 8.18.
Upgrade notes
Here's some important information you should know about:
8.18.1: Bundled JRE disables secure connections to MySQL Community Edition 5.7.27 or older over TLS versions 1 and 1.1
Jira 8.18.1 binary installers are bundled with the AdoptOpenJDK 8u291 JRE, which ships with TLS versions 1 and 1.1 disabled by default. This prevents secure connections with MySQL Community Edition 5.7.27 or older compiled with yaSSL.
You're not affected by this issue if:
- You’re running MySQL Enterprise Edition
- You’re running MySQL Community Edition 5.7.27 compiled with OpenSSL
- You haven’t enabled secure connections in MySQL Community Edition
- You’re running Jira using a JRE version lower than 8u291 or 11.0.11
To ensure that Jira can establish a secure connection with your MySQL database after the upgrade, switch to a version of MySQL Community Edition that supports TLS 1.2. You can choose one of the following solutions:
Recommended solution: Upgrade to MySQL Community Edition 5.7.28 or newer
Because the binary distributions of MySQL Community Edition 5.7.27 and older are compiled with yaSSL, they do not support TLS 1.2 by default. We recommend that you upgrade to MySQL Community Edition 5.7.28 or newer (this version uses the OpenSSL library), and then allow secure connections over TLS 1.2 by either:
- Upgrading the MySQL Connector/J driver to version 8.0.19 or newer.
- Adding the
enabledTLSProtocols=TLSv1.2parameter to the MySQL JDBC connection string indbconfig.xml.
For more information, see:
- MySQL 5.7 Reference Manual — 2.11 Upgrading MySQL
- 2023-03-06_08-25-28_Connecting Jira applications to MySQL 5.7
Solution 2: Recompile MySQL Community Edition 5.7.27 or older with OpenSSL
Alternatively, you can recompile version MySQL Community Edition 5.7.27 or older with OpenSSL, and then allow secure connections over TLS 1.2 by either:
- Upgrading the MySQL Connector/J driver to version 8.0.19 or newer.
- Adding the
enabledTLSProtocols=TLSv1.2parameter to the MySQL JDBC connection string indbconfig.xml.
For more information, see:
- MySQL 5.7 Reference Manual — 2.9.6 Configuring SSL Library Support
- 2023-03-06_08-25-28_Connecting Jira applications to MySQL 5.7
Solution 3: Re-enable TLS 1 and 1.1 in Java
The TLS 1 and 1.1 protocols are insecure. Atlassian does not recommend using this solution in the long term.
If required, you can re-enable support for TLS 1 and TLS 1.1 in Java by removing the TLSv1 and TLSv1.1 entries from the jdk.tls.disabledAlgorithms property in <JAVA_HOME>/lib/security/java.security.
Disable the PacClient
Use this temporary workaround only if you installed Jira Core 8.18.0. This problem has been fixed in 8.18.1.
Jira Core 8.18.0 had a known issue that affected Universal Plugin Manager (UPM) cache invalidation and rendered Jira unresponsive after a few hours since startup.
To prevent Jira from becoming unresponsive, disconnect it from the Atlassian Marketplace:
- Select Administration (
) > Manage apps. - At the bottom of the page, select Settings.
- Clear the Connect to the Atlassian Marketplace checkbox and select Apply.
Alternatively, you can restart Jira with the -Dupm.pac.disable=true startup option enabled. See Setting properties and options on startup .
After disabling the PacClient, you won’t be able to install or update apps directly from the Atlassian Marketplace. However, you can still do that by manually uploading apps from the Manage apps administration page.
H2 database upgrade
In this release we've upgraded the embedded H2 database, which is often used when evaluating Jira. This is a significant upgrade which contains some breaking changes.
If you attempt to upgrade Jira running on the embedded H2 database, follow this procedure:
- Create XML backup from the instance to be upgraded.
- Remove h2db.mv.db file (from ${jira_home}/database).
- Run the new Jira instance.
- Restore XML backup
Migrate your data to a supported database
If you are using H2 in production, you will need to migrate to a supported external database before upgrading your instance.
See Switching databases for a step by step gui
End of support announcements
Here are the changes to supported platforms in this version:
- Deprecating PostgreSQL 9.6: We're deprecating PostgreSQL 9.6, and plan to remove it in Jira Core 8.19.
Deprecating Microsoft Edge Legacy: After introducing support for Microsoft Edge (Chromium), we've deprecated Microsoft Edge Legacy, but you can still use it with this version.
For the list of supported platforms, see Supported platforms .
App developers
See Preparing for Jira 8.18 for any important changes regarding apps.
Upgrade procedure
Upgrading from a Jira version 8.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.