JIRA Service Desk 3.9 Enterprise release change log

JIRA Service Desk 3.9.x upgrade notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

JIRA Service Desk 3.9 is an Enterprise Release, and this change log aims to give you an overview of what's changed in the earlier versions. 

About Enterprise releases
We recommend upgrading JIRA Service Desk regularly, however if your organisation's process means you only upgrade about once a year, upgrading to an Enterprise 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. 

All changes are divided according to 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.3 to 3.9.

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, you won't be able to receive support for it. Here are the EOL dates for JIRA Service Desk 3.3 and JIRA Service Desk 3.9.

3.3 January 3, 2019

Learn more

3.9 November 14, 2019

Top features

Here's a summary of the great new features awaiting your users.  

3.3
  • Group customers into organizations.
  • Customize email notifications.
  • Agents can add portal announcements.
  • Rich text editing.
  • Project administrators can edit their project workflow.
  • Changes to starting a JIRA instance.
  • Data Centre single sign-on.
Release Notes
3.4
  • Updated project templates.
Release Notes
3.5
  • Non-customer comments enabled.
  • Creating customers from email address lists.
Release Notes
3.6
  • Improved SLA rendering.
  • Extended project administration.
  • JIRA Service Desk Data Centre zero downtime upgrades.
  • Improvements to issue export.
  • In-app notifications.
Release Notes
3.7
  • Canned responses.
Release Notes
3.8
  • Importing SLAs from existing projects.
  • Events for linked issues.
  • Syntax highlighting for new languages.
Release Notes
3.9
  • Better canned responses.
  • Auto approvals.
  • Live monitoring with JMX.
  • Better security with X-Frame-Options.

  • More languages supported.

  • Priority schemes from 3.9.4 only.
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.2. 

Supported platform changes

From time to time we will add or end support for a platform. Here's a summary of the changes since 3.3. 

3.3 No changes Supported platforms
3.4 No changes Supported platforms
3.5

Ended support for:

  • Microsoft SQL Server 2008
  • Postgres 9.0 and 9.1
  • MySQL 5.1
  • Internet Explorer 10
Supported platforms
3.6 No changes Supported platforms
3.7

Ended support for:

  • Postgres 9.2
Supported platforms
3.8 No changes Supported platforms
3.9 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. 

3.3
  • If you're upgrading to JIRA Service Desk 3.3 and MySQL 5.7.6 or above, you need to make sure your JIRA user has the REFERENCES permission.
  • If you're running your JIRA application over SSL, and have configured Apache Tomcat with HTTPS, you'll need to update your server.xml HTTPS connector with the correct protocol or JIRA will fail to start.
Upgrade Notes
3.4

No known issues.

Upgrade Notes
3.5

Performance issues:

  • Versions 3.5.1 and 3.5.2 have performance issues and show errors while opening pages or finishing some actions. This applies only if you’re using postgreSQL and have more than 500k users.
Upgrade Notes
3.6

Important notes:

  • If you're planning to use MySQL 5.7.6 or later, you'll need to grant your database user an extra permission (REFERENCE).
  • If you're running JIRA over SSL, you'll need to update your server.xml with the correct protocol because of the Apache Tomcat upgrade.
  • We've disabled automatic XML backups. Use your native database tools to create a backup.
Upgrade Notes
3.7

Important notes:

  • New options added to the startup files to enable garbage collection. Just a heads up, no actions required.
Upgrade Notes
3.8

Important notes:

  • New JDBC driver for Microsoft SQL Server requires a new URL. If you didn't modify the original URL, you can fix it with JIRA configuration tool. If you customized the URL, you might need to change it manually.
Upgrade Notes
3.9

Important notes:

  • Changes to priority schemes (project-specific priorities feature) will not affect your current configuration.

Known issues:

  • A fix for duplicated job IDs requires extra steps in some instances, just to be sure (checking the database if the index was created; restarting your JIRA instance.)
Upgrade Notes

Upgrade procedure

You can upgrade to JIRA Service Desk 3.9 Enterprise Release like any other version. We recommend that you upgrade directly to 3.9, without any intermediary versions. Use one of the following methods:


Upgrade Now


Last modified on Mar 7, 2018

Was this helpful?

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