JIRA Service Desk 3.6.x upgrade notes

Release notes for earlier versions of Jira Service Management

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This JIRA Service Desk release has reached its end of life. See End of life policy.

Please follow the instructions in the general Upgrading JIRA applications guide, as well as the JIRA Service Desk 3.6.x specific instructions below. The general guide contains important tasks that are essential for getting your upgraded JIRA installation to work correctly and, if necessary, migrating existing configurations.

You should also make sure that your licenses and add-ons are all up-to-date. Removing any incompatible add-ons before upgrading may help you avoid problems during your upgrade process. You can check the compatibility of your add-ons before your upgrade using the JIRA update check.

This page describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA Service Desk 3.6.x.

Information for JIRA developers

As JIRA Service Desk 3.6 runs on the JIRA 7.4 platform, see Preparing for JIRA 7.4 for important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.

Information for administrators

Performance issues

We’ve noticed that versions 3.6.0, 3.6.1 and 3.6.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. To work around it, increase the heap size by 1GB per million users. We’ll release a fix for this in the next bugfix release.

Modified startup files

We’ve added new options to the setenv.bat / setenv.sh file to enable garbage collection (GC) logging on JIRA startup. GC logs can be used to monitor the performance of JIRA by indicating when Java is collecting garbage, how long this process takes, and which resources can be freed. When you start the upgraded JIRA, the new log files will be stored in <installation-directory>/logs. For more info on GC logging, see Using garbage collection logs.

These are the new options:

-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -Xloggc:"%atlassian_logsdir%\atlassian-jira-gc-%%t.log"

Version specific detail

Check the JIRA application compatibility matrix to ensure you have the most up to date, compatible versions.

  • Upgrading from a 3.1 or later version - There are no known issues.
  • Upgrading from a 3.0 - There is a known issue regarding gadgets, and there is a workaround described in the JIRA Service Desk 3.1.x upgrade notes.
  • Upgrading from a version earlier than 3.0 - Please consult the Migration hub  as it contains information on important user management, application access and log in changes. You must upgrade to JIRA Service Desk 3.0 before upgrading to JIRA Service Desk 3.6.
Last modified on Jul 22, 2019

Was this helpful?

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