Jira Service Desk 3.15.x upgrade notes
Here are some important notes on upgrading to Jira Service Desk 3.15. For details of the new features and improvements in this release, see the Jira Service Desk 3.15 release notes. As Jira Service Desk runs on the Jira platform, you should also view the Jira platform 7.12 upgrade notes.
Upgrade notes
End of support announcement for com.atlassian.fugue
Jira Service Desk 3.15 has deprecated the use of com.atlassian.fugue. In Jira Service Desk 4.0, we'll be permanently removing it and updating our APIs to use Core Java Data types and Exceptions instead. We're doing this to make life easier for the folks who develop on Jira Service Desk.
What this means for you
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.
You can start testing these changes in Jira’s 8.0 Early Access Program (EAP), so keep an eye on our Jira Server Developer docs for the latest updates, or post any questions in the Atlassian Developer Community and we'll get back to you.
Jira administrators
Apache Tomcat upgrade
In Jira Service Desk 3.15.2, we’ve upgraded Apache Tomcat to version 8.5.32, which means you'll need to change the server.xml file. If you installed Jira Service Desk 3.15.2 (this release has been pulled), you can already make these changes. If not, then you’ll need to make them when upgrading to 3.15.3, or any later version.
These changes are needed to avoid a bug related to JQL search panel. More about this bug here.
Steps:
- Go to
<Jira-installation-directory>/conf, and edit theserver.xmlfile. - Find all connectors your application is using. Just search for Connector in the file, or look at the example below.
Add
relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"to the connector properties inserver.xml. For example:<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>- Restart Jira.
PostgreSQL 9.3 deprecated
Jira 7.12 has deprecated the use of PostgreSQL 9.3. In Jira 8.0, we'll be permanently removing support for PostgreSQL 9.3. For more info, see End of support announcements.
New events in the audit log (filters and dashboards)
As described in the release notes, your 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. Learn more about viewing the audit log.
Plugin developers
See Preparing for Jira 7.12 for any important changes regarding plugins.
Upgrade procedure
Note: Upgrade to a test environment first. Test your upgrades in your test environment before rolling them into production.
If you're already running a version of Jira, please follow these instructions to upgrade to the latest version:
- Before you upgrade, we strongly recommend that you back up your installation directory, home directory, and database.
- Read the release notes and upgrade notes for all releases between your version and the latest version.
- Download the latest version of Jira Service Desk.
- Follow the instructions in the Upgrade Guide.
Upgrading from earlier versions?
Check the Jira application compatibility matrix to ensure you have the most up to date, compatible versions.
- 3.1, or later
There are no known issues. - 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. - 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.15.