Jira Service Desk 4.5.x Long Term Support release change log

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Jira Service Desk 4.5 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 Desk regularly. However, if your organisation'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 be receive support for it. Here are the EOL dates for Jira Service Desk 3.9, 3.16, and 4.5.

4.521 October, 2021Learn more
3.1628 November, 2020
3.913 November, 2019



Top features

Here's a summary of the great new features awaiting your users, in each release between 3.9 and 4.5.  

4.5
  • No new features, to keep things smooth and stable
4.4
  • More control over SLA calendars
  • Issue archiving in Jira Service Desk Data Center
  • Browse permission works as expected
  • Filters in 'Multi user picker' custom field
  • Batching emails by default
  • External links open in a new tab
  • Filters to browse archived issues
  • Jira becomes more accessible
Release notes
4.3
  • Search got smarter
  • Limited threads to boost performance
  • New filters to search for custom fields
  • List of custom changes after upgrade
  • Browsing projects is faster
  • AdoptOpenJDK bundled with Jira
  • Cluster lock mechanism improvements
  • Reindexing made easier
  • Content Deliver Network (CDN) for Jira Data Center
Release notes
4.2
  • Edit custom fields in automation
  • Better knowledge base search experience
  • Enhanced knowledge base reports
  • Jira Service Desk source code available
  • New colors for issue statuses
  • Support for Java 11
  • Support for Microsoft SQL Server 2017
  • Export more issues to CSV
Release notes
4.1
  • New customer portal experience
  • Smarter automation webhooks
Release notes
4.0
  • Lucene upgrade to power performance
  • jQuery upgrade
  • Accessible priority icons
  • New options in advanced search
  • AUI upgrade
  • AdoptOpenJDK support
Release notes
3.16
  • OpenJDK comes to Jira
Release notes
3.15
  • SLAs based on due date
  • Share edit rights for filters and dashboards
  • New look for the Custom fields page
  • Customer fields optimizer for Data Center
Release notes
3.14
  • New look and feel for Jira Service Desk
  • Project archiving for Data Center
  • IPv6 support
  • Jira Service Desk available in Dutch
  • New columns for projects
Release notes
3.13
  • New events in the audit log
Release notes
3.12
  • Approve requests from email
  • Search versions with a wildcard
  • Microsoft SQL Server 2016 support
Release notes
3.11
  • Improved quick search
Release notes
3.10
  • Account verification emails
  • Visibility on approvals
Release notes
3.9
  • Priorities per project (from 3.9.4)
  • Better canned responses
  • Auto approvals
  • Live monitoring with JMX
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 3.9. 

Versions 4.0 to 4.5...
4.5

Summary
Loading...
Refresh


4.4

Summary
Loading...
Refresh

All 4.4 bug fixes
4.3

Summary
Loading...
Refresh

All 4.3 bug fixes
4.2

Summary
Loading...
Refresh

All 4.2 bug fixes
4.1

Summary
Loading...
Refresh

All 4.1 bug fixes
4.0

Summary
Loading...
Refresh

All 4.0 bug fixes
Versions 3.9 to 3.16...
3.16

Summary
Loading...
Refresh

All 3.16 bug fixes
3.15

Summary
Loading...
Refresh

All 3.15 bug fixes
3.14

Summary
Loading...
Refresh

All 3.14 bug fixes
3.13

Summary
Loading...
Refresh

All 3.13 bug fixes
3.12

Summary
Loading...
Refresh

All 3.12 bug fixes
3.11

Summary
Loading...
Refresh

All 3.11 bug fixes
3.10

Summary
Loading...
Refresh

All 3.10 bug fixes
3.9

Summary
Loading...
Refresh

All 3.9 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 3.9. 

4.5

No changes.

4.4

Added support for:

  • Aurora PostgreSQL for Jira Data Center
  • Oracle 18c and 19c

Ended support for:

  • Jira native importers available in the Jira Importers Plugin (JIM)
  • Advance notice: Createmeta REST endpoint
Supported platforms
4.3

Added support for:

  • Oracle 12c Release 2
Supported platforms
4.2

Added support for:

  • Java 11
  • Microsoft SQL Server 2017

Ended support for:

  • 32-bit installers
Supported platforms
4.1No changes.Supported platforms
4.0

Added support for:

  • Apache Tomcat 8.5.35 (replacing 8.5.32). Added in Jira 8.0.1.

Ended support for:

  • Fugue removed
  • PostgreSQL 9.3
  • MySQL 5.5
Supported platforms
3.16

Added support for:

  • AdoptOpenJDK 8
Supported platforms
3.15

Added support for:

  • Apache Tomcat 8.5.32 (replacing 8.5.29)

Ended support for:

  • Fugue
Supported platforms
3.14

Added support for:

  • Apache Tomcat 8.5.29 (replacing 8.5.6)
Supported platforms
3.13No changes.Supported platforms
3.12No changes.Supported platforms
3.11No changes.Supported platforms
3.10No changes.Supported platforms
3.9No 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. 

4.5

No updates.

4.4

Important notes:

  • We're now supporting Aurora PostgreSQL for Jira Data Center
  • Due to some security updates you need to review your filter and dashboard permissions.
  • Email notifications are batched by default.
  • Tomcat upgraded to version 8.5.42.
  • We are now supporting Oracle 18c and 19c.
  • We've added a new set of alerts to help you monitor your Data Center.
Upgrade notes
4.3

Important notes:

  • Jira is now bundled with AdoptOpenJDK 8 instead ofOracle's JDK. If you're installing Jira manually, you need to install JDK.
  • We have upgraded the atlassian-jslibs plugin from version 1.2.5 to 1.4.1 and are now bundling React 16.8.6, ReactDOM 16.8.6 factory, and Marionette 4.1.2 with Jira.
  • When you upgrade you need to reapply any custom changes you've made to your old Jira files to the same files in the upgraded version. We will show you a list of files with custom changes.
  • To fix issues importing a backup from Jira Cloud into Jira Server, we needed to change the database column size. Now, Jira might start up slower after upgrade, especially if you're using MySQL database.
  • You can now encrypt your database password stored in the dbconfig.xml file.
  • We improved the cluster lock mechanism in Jira DC by introducing lock timeouts. When a node loses a cluster lock it will be automatically recoverable without any actions from administrator.
Upgrade notes
4.2

Important notes:

  • We've upgraded the Microsoft JDBC driver, bundled with Jira, to 7.2.1. This versions is required for Java 11 support.
  • Jira installers are now bundled with AdoptOpenJDK JRE 8 instead of Oracle JDK. If you're using the installer, check your Java version after the upgrade, as Jira might have switched to AdoptOpenJDK.
Upgrade notes
4.1

Important notes:

  • We are deprecating 32-bit installers, and they will be removed in the upcoming release.
  • We are deprecating the CDN dark feature, and are planning to remove it in the upcoming release. We'll replace it with an official CDN support for Jira Data Center.
Upgrade notes
4.0

Important notes:

Index changes...
  • Incompatible index: Due to the upgrade of the library responsible for the Jira index, your current index will become incompatible. You'll need to create a new index by reindexing Jira after the upgrade.
  • Index location changes: Starting from Jira 8.0, the Jira index will be stored in a new location: <Jira-home-directory>/caches/indexesV1.
  • Automatic reindex: Because of the above changes, Jira will trigger an automatic reindex after the upgrade, which might mean you'll need to reindex twice following the upgrade. Since this might be really time-consuming for large Jira instances, you can disable the automatic reindex, and run it manually whenever you're ready
App changes...
  • Incompatible apps: You'll need to disable all apps that are incompatible with the new version before the upgrade. Incompatible apps might block the upgrade or the Jira startup after the upgrade.
Other changes...
  • Reduced logging: Application log output (atlassian-jira.log) is no longer mirrored in the Tomcat log file, catalina.out, to preserve the disk space.
  • Jira needs more memory: We've increased the default heap size available to Jira to 2GB. Note that this change requires extra steps if you're using 32-bit systems.
  • Zero downtime upgrades: This upgrade method won't be available when upgrading from Jira 7.x to Jira 8.x. Once you're on Jira 8.x, you can use it to upgrade to any later version.
End of support...

In Jira Service Desk 4.0, we've removed com.atlassian.fugue, and updated our APIs to use Core Java Data types and Exceptions. We’ve introduced this change to make it easier to develop on Jira Service Desk.

What you'll need to do
Before using Core Java Data types and Exceptions, update any scripts, integrations, or apps that make requests to endpoints returning com.atlassian.fugue. This stops them breaking after the update.

Read our Java API docs and REST API docs to learn how.

Upgrade notes
3.16
  • We've upgraded Apache Tomcat to version 8.5.32, which requires you to make changes to the server.xml file.
  • Jira 7.12 and 7.13 have deprecated the use of PostgreSQL 9.3.
  • You can run Jira on OpenJDK 8.
  • We've added properties for configuring the JVM code cache to the setenv.sh /.bat file.
Upgrade notes
3.15
  • Jira Service Desk 3.15 has deprecated the use of com.atlassian.fugue. You'll need to update any scripts, integrations or apps that make requests to endpoints returning com.atlassian.fugue, to use Core Java Data types and Exceptions.
  • Jira 7.12 has deprecated the use of PostgreSQL 9.3.
  • New events in the audit log (filters and dashboards). Users can now share their filters and dashboards with permission to edit. We'll notify you about every change through new events in the audit log.
Upgrade notes
3.14
  • Apache Tomcat upgraded to version 8.5.29.
  • IPv6 support. We’ve taken the dual-stack approach (IPv4 + IPv6), so your IPv4 addresses will still work, and there are a few things you need to be aware of:
    • Must allow IPv4 traffic
    • Avoid using raw IPv6 addresses anywhere in the Jira configuration
    • Avoid using raw IPv6 addresses in the browser
    • AWS Relational Database Service (RDS) doesn't support IPv6
    • Problems with cache replication for Jira Data Center on Linux
Upgrade notes
3.13No updates.Upgrade notes
3.12
  • Instructions to connect Jira to a Microsoft SQL Server 2016 database.
Upgrade notes
3.11
  • Monitoring the quick search. We’ve added extra options to the new quick search to let Jira admins limit the number of searches, and monitor how users are searching in real-time.
Upgrade notes
3.10
  • Oracle JDBC driver no longer bundled with Jira.
  • Account verification emails can now be disabled.
Upgrade notes
3.9
  • Priority schemes (UI changes). We've made significant changes to how priorities are managed in Jira, but these changes are only available from Jira Service Desk 3.9.4.
Upgrade notes
Last modified on Jun 26, 2020

Was this helpful?

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