Jira Service Desk 4.3.x upgrade notes
Below are some important notes on upgrading to Jira Service Desk 4.3. For details on the new features and improvements in this release, see the Jira Service Desk 4.3 release notes.
As Jira Service Desk runs on the Jira platform, you should also view the Jira platform 8.3 upgrade notes.
Summary of changes
Upgrade notes
Here's a summary of changes and important notes from Jira Service Desk 4.3.
AdoptOpenJDK 8 bundled with Jira
Jira is now bundled with AdoptOpenJDK JRE 8 instead of Oracle JDK. This only applies to Jira installers, as the archives don’t include any Java. If you're installing Jira manually from the archive, you'll need to install JDK yourself.
Support for Oracle 12c Release 2
We've added support for Oracle 12c Release 2 database which remains under Oracle's Premier Support. See Supported platforms.
atlassian-jslibs bumped to 1.4.1
We've upgraded the atlassian-jslibs app from version 1.2.5 to 1.4.1, and are now bundling React 16.8.6, ReactDOM 16.8.6 factory, and Marionette 4.1.2 with Jira.
List of custom changes after upgrade
When you upgrade you need to reapply the custom changes made to your old Jira files to the same files in the upgraded version of Jira. Previously, we couldn't tell you which files you'd modified. Now we can. When you start Jira after your upgrade, you'll see a list of files that have been modified so you can easily transfer the changes.
Migrating from Jira Cloud to Jira Server
To fix an issue when importing a backup from Jira Cloud into Jira Server, we needed to change the database column size. As a result, Jira might start up slower just after upgrade, especially if you are using a MySQL database. On the upside, the migration process finishes with no exceptions.
Encrypting database password
You can now encrypt your database password stored in the dbconfig.xml file. We've prepared two encryption methods for basic and advanced users, and also a way to create your own Cipher. Learn more at Encrypting database password.
Cluster lock mechanism improved in Data Center
We've made the cluster lock mechanism in Jira Data Center safer by introducing lock timeouts. Previously, if a node lost a cluster lock you had to restart that node to recover. Now, when a node loses a cluster lock it can be recovered automatically so your Jira admin doesn't have to do anything. Learn more at JRASERVER-66597 - Getting issue details... STATUS
End of support announcements
We're making the following changes:
- Advance notice: End of support for several built-in importers. In Jira 8.4, we will drop support for built-in importers dedicated to specific applications, like Asana, Bugzilla, Pivotal Tracker. You will still be able to import data to Jira, provided that you use CSV or JSON format.
- Removed Jira CDN dark feature. The unsupported Jira CDN dark feature
jira.fixed.cdn.enableand system propertyjira.fixed.cdn.prefixhas been removed in Jira 8.4. We recommend you turn off this dark feature, and remove the system property from yoursetenv.shorsetenv.batfile.
For more information, see End of support announcements.
App developers
See Preparing for Jira 8.3 for any important changes regarding apps.
Upgrade procedure
See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps that are required for Jira Service Desk 4.3.