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

Jira Service Desk 3.16.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 3.16 is a Long Term Support release, and this change log aims to give you an overview of what's changed in the preceding versions. 


About Long Term Support releases
 We recommend upgrading Jira Service Desk regularly. That said, 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. It provides continued access to critical security, stability, data integrity and performance issues, until this version reaches end of life.

 

What's covered

All changes are divided according to the versions in which they were released, but it doesn't mean you have to upgrade through each version separately. You can go straight from 3.9 to 3.16.



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 and 3.16.

3.9 November 14, 2019

Learn more

3.16November 28, 2020



Top features

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

3.9

  • Priorities per project (from 3.9.4)

  • Better canned responses

  • Auto approvals

  • Live monitoring with JMX

Release notes
3.10

  • Account verification emails

  • Visibility on approvals

Release notes
3.11
  • Improved quick search
Release notes
3.12

  • Approve requests from email

  • Search versions with a wildcard

  • Microsoft SQL Server 2016 support

Release notes
3.13
  • New events in the audit log
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.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.16
  • OpenJDK comes to Jira
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. 

3.9

Summary
Refresh

All 3.9 bug fixes
3.10

Summary
Refresh

All 3.10 bug fixes
3.11

Summary
Refresh

All 3.11 bug fixes
3.12

Summary
Refresh

All 3.12 bug fixes
3.13

Summary
Refresh

All 3.13 bug fixes
3.14

Summary
Refresh

All 3.14 bug fixes
3.15

Summary
Refresh

All 3.15 bug fixes
3.16

Summary
Refresh

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

3.9

No changes.

 Supported platforms
3.10No changes. Supported platforms
3.11

No changes.

Supported platforms
3.12No changes.Supported platforms
3.13

No changes.

Supported platforms
3.14

Added support for:

  • Apache Tomcat 8.5.29 (replacing 8.5.6)
Supported platforms
3.15

Added support for:

  • Apache Tomcat 8.5.32 (replacing 8.5.29)
Supported platforms
3.16

Added support for:

  • AdoptOpenJDK 8
 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. 

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
3.10
  • Oracle JDBC driver no longer bundled with Jira.
  • Account verification emails can now be disabled.
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.12
  • Instructions to connect Jira to a Microsoft SQL Server 2016 database.
Upgrade notes
3.13

No updates.

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



Upgrade procedure

You can upgrade to the Jira Service Desk 3.16 Long Term Support release like to any other version. We recommend that you upgrade directly to 3.16, without any intermediary versions.

Use one of the following methods:



Upgrade now

Last modified on Jun 26, 2020

Was this helpful?

Yes
No
Provide feedback about this article

Related content

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