Jira Service Management 5.4.x Long Term Support release change log
Jira Service Management 5.4 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.
Jump to...
End of Life policy
Atlassian supports feature versions for two years after the first major iteration of that version was released. Once a version reaches End of Life (EOL), you won't receive support for it. Here are the EOL dates for Jira Service Management 5.4, 4.20, and 4.13. Learn more
5.4 | 15 November 2024 | Learn more |
|---|---|---|
4.20 | 19 October 2023 | |
4.13 | 8 October 2022 |
Version compatibility
Each version of Jira Core, Jira Software, and Jira Service Management is compatible with a specific version of the other applications. Here’s the compatibility for Jira Service Management 4.13, 4.20, and 5.4. Learn more
Jira Core | Jira Software | Jira Service Management |
| 9.4 | 9.4 | 5.4 |
8.20 | 8.20 | 4.20 |
8.13 | 8.13 | 4.13 |
Top features
Here's a summary of the great new features awaiting your users, in each release between 4.13 and 5.4.
| 5.4 |
| Release notes |
|---|---|---|
| 5.3 |
| Release notes |
| 5.2 |
| Release notes |
| 5.1 |
| Release notes |
| 5.0 |
| Release notes |
| 4.22 |
| Release notes |
| 4.21 |
| Release notes |
4.20 |
| |
4.19 |
| |
4.18 |
| |
4.17 |
| |
4.16 |
| |
4.15 |
| |
4.14 |
| |
4.13 |
|
Critical bug fixes
Every release contains a bunch of bug fixes. Here's all the ones that were deemed critical severity, and fixed since 4.13.
Supported platform changes
From time to time we'll add or end support for a platform. Here's a summary of the changes since 4.13.
| 5.4 | No changes | Supported platforms |
|---|---|---|
| 5.3 | No changes | Supported platforms |
| 5.2 | Ended support for:
| Supported platforms |
| 5.1 | No changes | Supported platforms |
| 5.0 | Added support for:
| Supported platforms |
| 4.22 | Added support for:
| Supported platforms |
| 4.21 | No changes | Supported platforms |
4.20 | Ended support for:
| |
4.19 | Added support for:
End support for:
| |
4.18 | No changes | |
4.17 | Added support for:
| |
4.16 | No changes | |
4.15 | No changes | |
4.14 | No changes | |
4.13 | No changes |
Technical upgrade notes
This table is a high level summary of the upgrade notes, you should read the full upgrade notes before upgrading.
| 5.4 | No important changes | |
| 5.3 | No important changes | Upgrade notes |
| 5.2 |
| Upgrade notes |
| 5.1 |
| Upgrade notes |
| 5.0 |
| Upgrade notes |
| 4.22 |
| Upgrade notes |
| 4.21 | No important changes | Upgrade notes |
4.20 | No important changes | |
|---|---|---|
4.19 |
| |
4.18 |
| |
4.17 |
| |
4.16 |
| |
4.15 |
| |
4.14 |
| |
4.13 | No important changes |
Known issues
| Issue | Solution |
|---|---|
| The user receives an error message when accessing Project settings if no Assets 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 without assigned Assets roles receive an error message when when accessing Kanban boards. | This is a known issue we're going to fix in Jira 5.4.1. The issue is tracked in the following 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. |