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

Jira Service Desk 4.13.x upgrade notes

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Jira Service Desk 4.13 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.

 

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 be able to receive support for it. Here are the EOL dates for Jira Service Desk 3.16, 4.5, and 4.13.

4.138 October, 2022Learn more
4.521 October, 2021
3.1628 November, 2020

Top features

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

4.13

This is a Long Term Support release.

  • No new features, to keep things smooth and stable
Release notes
4.12
  • Managing Opsgenie incidents in Jira Service Desk
  • Using Confluence Cloud as your knowledge base
  • Jira Service Desk support on mobile (Beta)
  • OAuth 2.0 support for Microsoft
  • Changes to how users are displayed in the user picker
  • More control over your Advanced Audit log (Data Center)
  • Less app impact on indexing (Data Center)
  • Users created automatically with Just-in-time user provisioning (Data Center)
Release notes
4.11
  • Multilingual customer portal and help center
  • Advanced auditing (Data Center)
  • Managing private filters and dashboards
  • Embedded Crowd upgrade
  • Max timeout for the Favorite Filters gadget
  • Configuring how fast stale nodes are moved offline (Data Center)
Release notes
4.10
  • OAuth 2.0 support for incoming mail
  • User anonymization (GDPR) improvements
  • More insight into your custom fields (Data Center)
  • Stale nodes automatically removed (Data Center)
Release notes
4.9
  • Adding an option to control sharing settings for new requests created both via email and customer portal (addition to sharing settings from Jira Service Desk 4.7)
  • Node and application status for Jira Data Center cluster monitoring
  • Accessibility: Text spacing
Release notes
4.8
  • Managing multiple issues at once with bulk actions
  • No more duplicate attachments in requests
  • Accessibility settings
  • Revamped audit log
  • Running Jira Data Center on a single node (available for all versions)
Release notes
4.7
  • Requests are private by default
  • Email verification
  • Changes in how agents are treated by Jira
  • Anonymizing users for GDPR compliance
  • OpenID Connect (Data Center)
Release notes
4.6
  • New portal is now default
  • Improvements to agent queues
  • REST API for managing agent queues
  • Previous and next search results
  • Users and roles made better
  • Custom changes transferred on upgrade
  • Suffix search
  • New health check: JVM code cache
  • Rate limiting (Data Center)
  • New events in the audit log (Data Center)
Release notes
4.5

This is a Long Term Support release.

  • No new features, to keep things smooth and stable

Release notes

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

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

Versions 4.6 to 4.13...
4.13

Summary
Refresh


All 4.13 bug fixes

4.12

Summary
Refresh

All 4.12 bug fixes
4.11

Summary
Refresh

All 4.11 bug fixes
4.10

Summary
Refresh

All 4.10 bug fixes
4.9

Summary
Refresh

All 4.9 bug fixes
4.8

Summary
Refresh

All 4.8 bug fixes
4.7

Summary
Refresh

All 4.7 bug fixes
4.6

Summary
Refresh

All 4.6 bug fixes
Versions 4.0 to 4.5...
4.5

Summary
Refresh


All 4.5 bug fixes

4.4

Summary
Refresh

All 4.4 bug fixes
4.3

Summary
Refresh

All 4.3 bug fixes
4.2

Summary
Refresh

All 4.2 bug fixes
4.1

Summary
Refresh

All 4.1 bug fixes
4.0

Summary
Refresh

All 4.0 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.13No changes.Supported platforms
4.12

Ended support for:

  • MySQL 5.6
  • Microsoft SQL Server 2014

Added support for:

  • MySQL 8.0
Supported platforms
4.11

Ended support for:

  • Hipchat app (also unbundled from Jira)
Supported platforms
4.10No changes.Supported platforms
4.9No changes.Supported platforms
4.8

Ended support for:

  • Microsoft SQL Server 2012
  • PostgreSQL 9.4, 9.5
  • Solaris
  • Oracle 12c R1
Supported platforms
4.7

Added support for:

  • PostgreSQL 11 and Aurora 3.0 for Jira Data Center
Supported platforms
4.6

Added support for:

  • PostgreSQL 10

Ended support for:

  • Internet Explorer 11
Supported platforms
4.5

No changes.

Supported platforms

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

Technical upgrade notes

This table is a high level summary of the upgrade notes, you should read the full upgrade notes before upgrading. 

4.13


Upgrade notes
4.12

Important notes:

  • Known issue: Azure SQL is reported as unsupported
  • Known issue: MySQL 8.0 is reported as misconfigured
  • We've added database password encryption.
  • We've extended API response to look for archived projects.
  • We've added new events in the Advanced audit log for Data Center.
  • We fixed a bug that caused issues removed from sprint not showing in Burndown Chart or Sprint Report. This required full reindex.
Upgrade notes
4.11

Important notes:

  • We fixed a bug that caused issues removed from sprint not showing in Burndown Chart or Sprint Report. This requires full re-index.
  • We fixed fetching updates from different products in Jira.
  • We upgraded Embedded Crowd in Jira from version 2.0 to 4.0.
  • We upgraded Apache Tomcat from 8.5.50 to 8.5.56.
  • Hipchat got unbundled from Jira.
Upgrade notes
4.10

Important notes:

  • If you're using Google or Microsoft for incoming mail, we recommend that you create an OAuth 2.0 integration, and reconfigure your mail servers and email channels.

Upgrade notes
4.9

Important notes:

  • New API to help the Versions view load faster

Upgrade notes
4.8

Important notes:

  • The new audit log requires that we migrate your current audit log entries. This might take some time, but it will be done in the background.
  • We've enabled Garbage First Garbage Collection (G1 GC) for Jira instances running on Java 11.
Upgrade notes
4.7

Important notes:

  • PostgreSQL 11 support
  • OpenID Connect support for Jira Data Center
  • Changes in the issue collector
  • Disabling HTML in custom fields description
  • Changing how agents are treated in SLAs and automation rules
  • Changed default behavior of sharing new requests with the customer’s organization
Upgrade notes
4.6

Important notes:

  • API change for JXM monitoring
  • Support for PostgreSQL 10
  • New JVM code cache check
  • New information in the audit log
  • Transferring custom modifications from old Jira files

  • Better support for reply emails from Outlook by mailhandlers

Upgrade notes
4.5

No updates.

Upgrade notes

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
Last modified on Oct 9, 2020

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.