JIRA Service Desk 3.3.x upgrade notes

Jira Service Management Release Notes

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.3.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. We introduced a new property in JIRA Service Desk 3.3 which allows you to start JIRA from the command line with your add-ons disabled.

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

On this page:

Information for JIRA developers

See Preparing for JIRA 7.3 for important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.

Information for administrators

Running JIRA on MySQL

MySQL introduced a change in MySQL 5.7.6 which requires your JIRA user for the data base to have the REFERENCES permission. 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 this permission.

Running JIRA applications over SSL

If you're running your JIRA application over SSL, and have already configured Apache Tomcat with HTTPS, you'll need to update your server.xml HTTPS connector with the correct protocol. If you don't, JIRA will fail to start. To update the required protocol:

  1. Make sure JIRA is stopped.
  2. Navigate to your server.xml page at <JIRA_INSTALL>/conf/server.xml.
  3. Locate your HTTPS connector, which will look something similar to this:

    <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
                  maxHttpHeaderSize="8192" SSLEnabled="true"
                  maxThreads="150" minSpareThreads="25"
                  enableLookups="false" disableUploadTimeout="true"
                  acceptCount="100" scheme="https" secure="true"
                  clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true"
                  keyAlias="jira" keystoreFile="<JIRA_HOME>/jira.jks" keystorePass="changeit" keystoreType="JKS"/>

    and change the protocol so that it looks more like this:

    <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
                  maxHttpHeaderSize="8192" SSLEnabled="true"
                  maxThreads="150" minSpareThreads="25"
                  enableLookups="false" disableUploadTimeout="true"
                  acceptCount="100" scheme="https" secure="true"
                  clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true"
                  keyAlias="jira" keystoreFile="<JIRA_HOME>/jira.jks" keystorePass="changeit" keystoreType="JKS"/>
  4. Save your changes.
  5. Start JIRA.

You may perform these steps during your upgrade, but make sure you perform them before you start JIRA at the end of the upgrade process.

Checking your project administrators

JIRA Service Desk 3.3 now allows project administrators to edit workflows that are specific to their project only. To help with checking who would be granted this permission, you can use a script we've provided to check you projects and corresponding project administrators. The script requires node.js and can be found in this Bitbucket repository

Version specific detail

  • 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.3.
Last modified on Jan 5, 2019

Was this helpful?

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