Jira Service Desk 3.16.x release notes
28 November 2018We're excited to bring you Jira Service Desk 3.16.
- Next Long Term Support release is coming
- AdoptOpenJDK 8 comes to Jira
- Improved install documentation
- Enterprise release round up
- Resolved issues
- Credit, where credit's due
Interested in trying a shiny new version? Don't forget to renew your active software maintenance. Renew now.
If you're looking for compatible Jira applications, look no further:
Jira Service Desk 3.16 is a Long Term Support release
This means we'll provide bug fix releases until 3.16 reaches end of life, to address critical security, stability, data integrity, and performance issues.
Ready to upgrade? Check out the Jira Service Desk 3.16 Long Term Support release change log for a roll-up of changes since 3.9.
Next LTS release is coming!
Jira Service Desk 4.5 will be our next Long Term Support release, coming around Q3 this year. If you’d like to jump on the latest and greatest Jira Service Desk 4, start planning for your upgrade by targeting this time frame.
AdoptOpenJDK 8 comes to Jira
You can now run Jira Service Desk on AdoptOpenJDK 8! We’re providing this as an option you can choose, however we’ll continue to bundle Jira with Oracle JDK.
Help us improve your install experience
We know that clear install instructions, with minimal noise and fuss, are vital to getting you set up. So we’re pleased to announce the new Jira Service Desk install guide.
To get you set up successfully, we’ve split the process out into stages that are clear and distinct. We also took special care to surface important information early, helping you avoid roadblocks before they happen.
Check it out at Installing Jira Service Management. And if you’re feeling generous, tell us what you think about it via the feedback link at the bottom of the page.
End of year Long Term Support release round up
It's been a few months since Jira Service Desk 3.9 was designated our first Long Term Support release, so let's look at how it compares to standard releases this year.
We made a new 3.9.x bug fix version available about every 4 to 6 weeks, and backported many important stability and performance fixes from later releases.
Organizations choose the Long Term Support release for different reasons. For some, it's the chance to schedule regular minor version upgrades throughout the year, and for others it's the ability to react quickly to a serious issue or vulnerability, without the overhead of upgrading to a new feature version.
Whether you choose an LTS release or a standard release, always remember to grab the most recent bug fix version to make sure your service desk is the best it can be.
If you'd like to upgrade to a new Long Term Support release, go ahead and download Jira Service Desk 3.16.1 (or any later bugfix), which has a number of backported fixes and improvements. The whole 3.16 line has been officially designated as an Enterprise release.
Released on 28 November 2018
Released on 29 January 2019
Released on 21 March 2019
Released on 19 April 2019
Released on 17 June 2019
Released on 9 July 2019
Released on 26 August 2019
We've omitted this release and went straight to 3.16.8. This was needed to release important fixes together.
Released on 16 September 2019
Released on 15 October 2019
The Atlassian Jira team is pleased to announce the release of Jira Service Desk 3.16.10.
Don't have Jira Service Desk 3.16.x yet?
Check out the new features and other highlights in the Jira Service Desk 3.16.x release notes .
Released on 6 November 2019
Released on 20 January 2020
Released on 27 February 2020
Released on 8 June 2020
Released on 20 July 2020
This release offers a flag to fix "Opening a random page on Jira with a user that is not authenticated will display "Page not found" (404 page) instead of the login page". Make sure the
jira.redirect.anonymous.404.errors flag is enabled for the fix to work.
Released on 10 August 2020
Released on 7 September 2020
Released on 12 October 2020
Our wonderful customers...
You play an important role in making Jira Service Desk better. Thanks to everyone who participated in interviews with us, made suggestions, voted, and reported bugs!