Jira 9.4 Long Term Support release upgrade guide
A Long Term Support (LTS) release is a combo of smart updates and robust stability. With LTS releases, we provide continuous access to security, stability, data integrity, and performance issues until a version reaches the end of its life.
Skip to
Why you should upgrade
Features highlight
Changes & improvements
Jira 9.4 comes with a number of changes, including features, supported platforms, and performance improvements:
- Jira Software change log: Get a quick roll-up of the most important changes in the latest versions.
- Jira Service Management change log: Get a quick roll-up of the most important changes in the latest JSM versions.
- Jira 9.4 REST API change log: Get a complete list of changes to Jira REST API in the latest versions.
- Cleanup guide: Get some tips and tricks on how to clean up your instance making it faster and more user-friendly.
Changes in supported platforms
By Jira 9.4, we’ve made changes to the following supported platforms:
- Removed support for PostgreSQL 9.6, MySQL 5.7, and Microsoft Edge Legacy
- Added support for Microsoft SQL Server 2019, PostgreSQL 12, PostgreSQL 14, and Amazon Aurora PostgreSQL 14 (Data Center only)
Critical bugs fixes
- The index replication service is paused indefinitely after failing to obtain an index snapshot from another node
- Jira "View on Board" link GHGoToBoard response time degrades with a number of boards
- Jira doesn’t create issues by email with the default reporter if the sender is associated with a user who is inactive or does not have a license
- Adding a group as a dashboard editor removes some individual users' right to edit a dashboard
- The Attachment button to embed attachments is not available when commenting during issue transition or comment edit
Learn more about bug fixes in Jira 8.20 to Jira 9.4
End of Life policy
Atlassian supports feature versions for two years after the first major iteration of a version was released. Once a version reaches the end of life (EOL), you won't be able to receive support for it. Here are the EOL dates for Jira Long Term Support releases. Learn more
Version | EOL date |
---|---|
8.13 | 8 November 2022 |
8.20 | 19 October 2023 |
9.4 | 31 January 2025 |
Compatible versions of your Atlassian suite
Make sure you know which Bamboo, Bitbucket, and Confluence versions are compatible with Jira 9.4 so that your stack is fully functional after the upgrade.
- Bamboo: versions 8.0 and later
- Bitbucket: versions 7.17 and later
- Confluence: versions 7.19 and later
- Before Confluence 7.17, there was an issue with this API endpoint that prevented full integration. The issue was fixed for Confluence 7.17, so make sure you’re upgrading to a more recent version. We recommend Confluence 7.19.
Upgrade procedure
Here's a summary of the upgrade path you'll be following.
Source version | 8.5, 8.13, 8.20 Already on 9.x? Go to our regular upgrade guide Upgrading from 7.x? Upgrade your Jira to version 8.13 first and proceed with upgrading from Jira 8.13 to Jira 9.4. |
---|---|
Target version | 9.4 |
Upgrade method and planned downtime |
|
Follow these guides to prepare for the upgrade and complete it successfully.
Known issues
Issue | Solution |
---|---|
After an upgrade to Jira 9.x, the Add comment button and the text box for new comments in issues are still showing at the bottom of the page, while the thread of comments is on top of them. | This is a known issue tracked in the ticket JRASERVER-74122 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
The performance check has shown some regression on the Browse Projects page starting from Jira 9.3. Due to this, the Browse Projects action performs around 10% slower, especially at scale on instances with a high number of projects. | This is a known issue we're going to fix in Jira 9.4.1. The issue is tracked in the ticket JRASERVER-74576 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
The user receives an error message when accessing Project settings if no Asset object schema exists and the user isn't in the jira-systems-administrators group. | This is a known issue tracked in the ticket JSDSERVER-12199 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
Some users get the following message while viewing Kanban boards: "Uncaught TypeError: Cannot read properties of null (reading 'innerText')". | This is a known issue we're going to fix in Jira 5.4.1. The issue is tracked in the ticket JSDSERVER-12124 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
The user may experience typing inverted text in the Text Area Attribute field when in Asset Object View in Jira Service Management. | This is a known issue in Jira Service Management (JSM) we're going to fix. The current workaround is to use Asset Schema View. This is tracked in JSDSERVER-12204 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
In Jira Service Management 5.3.0, free login on the customer portal was introduced. Because of this update, outgoing mail notifications might get delayed by many hours for any instance on JSM 5.3.0. | This is a known issue in Jira Service Management (JSM) we're going to fix. The issue is tracked in the ticket JSDSERVER-12279 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
In Jira Software, an outgoing mail configuration can't be saved using the JNDI Location setting. This issue impacts any Jira Server and Data Center version since Jira 9.2. | This is a known issue tracked in the ticket JRASERVER-74705 - Getting issue details... STATUS In the ticket, you can find a workaround instruction to save your outgoing mail configurations. Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |
The full reindex slows down for Jira 9.0.0. This is due to extra operations performed during Jira reindex that improve index correctness. | This is a known issue tracked in the ticket JRASERVER-74787 - Getting issue details... STATUS Feel free to leave comments on the ticket so we know your use cases better and understand how this issue is impacting your operations. |