Jira Service Management 5.4.x Long Term Support release change log

Still need help?

The Atlassian Community is here for you.

Ask the community

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.

 



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

31 January 2025

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

This is a Long Term Support release.

  • No new features, to keep things smooth and stable

Release notes
5.3
  • Login-free portal for easier access to customer portals (Data Center)

  • Insight is now Assets

  • Assets accessibility and UI enhancements

  • Column sorting on the My requests page in Help center (Data Center)

  • Batching database queries and additional disk caching during imports to Assets

  • New database connectivity metrics

Release notes
5.2
  • Help center announcement improvements

  • Background processing performance improvements

  • Insight accessibility and UI enhancements

  • OAuth2 authorization for SMTP outgoing mail servers

  • Diagnostic recording configuration with Java Flight Recorder

Release notes
5.1
  • New audit log for email channels

  • Insight accessibility and UI enhancements

  • Improved PSMQ information logging

  • Excluding events from the audit log (Data Center)

  • Improved indexing management at Jira start-up (Data Center)

  • Diagnosing and troubleshooting Jira with Java Flight Recorder

  • Prioritized search results in the issue navigator

  • App monitoring to help keep sites running smoothly

Release notes
5.0
  • Faster and more accurate SLA calculation (Data Center)

  • Insight accessibility and performance boost

  • Additions to auditing for Insight (Data Center)

  • Automation for Jira is now part of Jira Service Management Data Center (Data Center)

  • Secure application tunnels for connections to cloud products

  • Limiting excessive activity with Safeguards (Data Center)

  • New supported platforms

Release notes
4.22
  • Better communication with multiple email channels (Data Center)

  • New SLA configuration interface (Data Center)

  • Reusing data with auto-populated request fields (Data Center)

  • More data points to get a snapshot of your service team’s work

  • Login performance improvements for basic authentication

  • Excluding projects from the data pipeline

  • Configuring Jira as an OAuth 2.0 provider for better security

  • Accessibility improvements

Release notes
4.21
  • Customizing the requests list (Data Center)

  • Emoji comment reactions (Data Center)

  • Queues in the mobile app

  • Faster background processing

  • Project picker search improvements

  • Improved gadget configuration experience

Release notes

4.20

This is a Long Term Support release.

  • No new features, to keep things smooth and stable

Release notes

4.19

  • Approvers from Insight asset management (Data Center)

  • Better language support for asset management

  • Manually adjusting projects to better change management (Data Center)

  • Data pipeline improvements (Data Center)

  • Pagination and UI improvements on Screens

Release notes

4.18

  • Another bunch of vulnerabilities fixed in the Jira platform and Jira Service Management

  • Showing SLAs on customer portals (Data Center)

  • Turning off search bar on customer portals (Data Center)

  • Mentions on customer portals (Data Center)

  • Summary of mobile app improvements

  • Analyzing how issues change over time with data pipeline

Release notes

4.17

  • Around 100 security vulnerabilities fixed in the Jira platform

  • Over 20 security vulnerabilities fixed in Jira Service Management

  • Custom fields now included in data pipeline export (Data Center)

Release notes

4.16

  • Get more insights into the usage of custom fields (Data Center)

  • Bulk delete custom fields (Data Center)

  • Default values for the Description field (Data Center)

  • Let users log in with multiple identity providers (Data Center)

  • Check the status of your data pipeline exports (Data Center)

  • Keep Jira safe by disabling basic authentication

Release notes

4.15

  • Mindville's Insight - Asset Management is now part of Jira Service Management (Data Center)

  • Customer portal improvements (cards view in Help Center, rich text editor, voting for requests)

  • Official support for service projects in the Jira mobile app

  • Improved data insights, now also for Jira Service Management

  • Displaying image attachments in email notifications

Release notes

4.14

  • Jira Service Desk is now Jira Service Management

  • New events in the audit log (Data Center)

  • Email templates made better (Data Center)

  • Personal access tokens

  • Embedded Crowd and password encryption

  • Accessibility improvements when creating issues

  • Improved data insights (Data Center)

Release notes

4.13

This is a Long Term Support release.

  • No new features, to keep things smooth and stable

Release notes

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. 

Versions 4.21 to 5.4
5.4

Summary
Loading...
Refresh

All 5.4 bug fixes
5.3

Summary
Loading...
Refresh

All 5.3 bug fixes
5.2

Summary
Loading...
Refresh

All 5.2 bug fixes
5.1

Summary
Loading...
Refresh

All 5.1 bug fixes
5.0

Summary
Loading...
Refresh

All 5.0 bug fixes

4.22

Summary
Loading...
Refresh


4.21

Summary
Loading...
Refresh


Versions 4.13 to 4.20

4.20

Summary
Loading...
Refresh


4.19

Summary
Loading...
Refresh

All 4.19 bug fixes

4.18

Summary
Loading...
Refresh

All 4.18 bug fixes

4.17

Summary
Loading...
Refresh

All 4.17 bug fixes

4.16

Summary
Loading...
Refresh

All 4.16 bug fixes

4.15

Summary
Loading...
Refresh

All 4.15 bug fixes

4.14

Summary
Loading...
Refresh

All 4.14 bug fixes
4.13

Summary
Loading...
Refresh

All 4.13 bug fixes



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.4No changesSupported platforms
5.3No changesSupported platforms
5.2

Ended support for:

  • MySQL 5.7

Supported platforms
5.1No changesSupported platforms
5.0

Added support for:

  • PostgreSQL 14

Supported platforms
4.22

Added support for:

  • PostgreSQL 13

Supported platforms
4.21No changesSupported platforms

4.20

Ended support for:

  • Microsoft Edge Legacy


Supported platforms

4.19

Added support for:

  • PostgreSQL 12

End support for:

  • PostgreSQL 9.6

Supported platforms

4.18

No changes

Supported platforms

4.17

Added support for:

  • Microsoft SQL Server 2019

  • Microsoft Edge (Chromium)

Supported platforms

4.16

No changes

Supported platforms

4.15

No changes

Supported platforms

4.14

No changes

Supported platforms

4.13

No changes

Supported platforms

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
  • Insight accessibility and UI enhancements

  • OAuth 2.0 for outgoing mail

  • Diagnostic recording configuration with JFR

Upgrade notes
5.1
  • Improved indexing management at Jira start-up
Upgrade notes
5.0
  • Breaking changes in SLAs

  • Automation for Jira is now part of Jira Service Management Data Center

Upgrade notes
4.22
  • You can set up Jira as an OAuth 2.0 provider
Upgrade notes
4.21No important changesUpgrade notes

4.20

No important changes


Upgrade notes

4.19

  • Binary installers are now bundled with Java 11

  • You can specify how much CPU is used for the Activity Stream gadget

Upgrade notes

4.18

  • H2 database used for evaluation purposes has been upgraded to a newer version. You won't be able to upgrade without extra steps if you're using this database.

Upgrade notes

4.17

  • Deprecated JIM importers are now removed

Upgrade notes

4.16

  • Changes to data pipeline REST responses

Upgrade notes

4.15

  • We've made small tweaks to some of the email templates. These changes are optional for you.

  • We've made some changes to the web.xml file, so make sure to not copy over the old file after upgrading. This could affect attachments in Jira.

Upgrade notes

4.14

  • For Data Center, we'll move email templates from Jira resources to your Jira shared home directory on upgrade. If you customized the templates, read the upgrade notes for guidance on how to reapply your changes in 4.14.

Upgrade notes

4.13

No important changes

Upgrade notes

Known issues

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

Last modified on Nov 1, 2022

Was this helpful?

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