Jira Service Desk 4.1.x upgrade notes
Here are some important notes on upgrading to Jira Service Desk 4.1.
For details on the new features and improvements in this release, see the Jira Service Desk 4.1 release notes.
As Jira Service Desk runs on the Jira platform, you should also view the Jira platform 8.1 upgrade notes.
Here's a summary of changes and important notes from Jira Service Desk 4.1.
Jira might take longer to start after the upgrade for MySQL
For Jira Service Desk 4.1 we've added new columns to MySQL tables. This might result is Jira starting slower just after the upgrade.
Running Jira on Java 11
Java 11 is not officially supported yet, but you can already use it to run Jira. If you choose to do so, use JDK 11.0.2.
End of support announcements
In Jira Service Desk 4.1, we're making the following changes:
- Deprecating 32-bit installers. They will be fully removed in Jira Service Desk 4.2 or 4.3. If you need to stick to 32-bit systems, you can install by using the zip/tar.gz archives.
For more info, see End of support announcements.
We've made some look and feel changes to the help center and customer portal. This is the first round of improvements aimed at making the customer experience both simple and polished.
In order to do this, we've had to make some changes to the frontend codebase and this may impact third-party apps.
What's the potential impact?
There's two things to be aware of:
- layout changes may impact how your app looks within the customer portal
- the customer portal now loads routes asynchronously, which can impact previously available globals.
Web-resource dependencies with side-effects that are impacted:
Web-resource dependencies that expose AMD-modules that are impacted:
jira.webresources:calendar (contains the following AMD-Modules): jira/libs/calendar, jira/libs/calendar-layerable-mixin
jira.webresources:jquery (contains the following AMD-Modules): jquery, jira/jquery/deferred
jira.webresources:jira-logger (contains the following AMD-Modules): jira/util/logger
jira.webresources:jira-formatter (contains the following AMD-Modules): jira/util/formatter
jira.webresources:wrm-context-path (contains the following AMD-Modules): wrm/context-path
jira.webresources:feature-flags (contains the following AMD-Modules): jira/featureflags/feature-manager
jira.webresources:jira-metadata (contains the following AMD-Modules): jira/util/data/meta, jira/util/data/meta/store, jira/util/strings
com.atlassian.auiplugin:dialog2 (contains the following AMD-Modules): aui/dialog2
com.atlassian.auiplugin:aui-flag (contains the following AMD-Modules): aui/flag
jira.webresources:aui-core-amd-shim (contains the following AMD-Modules): aui/dialog, aui/dropdown, aui/message, aui/params, aui/progressive-data-set, aui/popup, aui/tabs, aui/inline-dialog
jira.webresources:jira-analytics-amd (contains the following AMD-Modules): jira/analytics
jira.webresources:util (contains the following AMD-Modules): jira/legacy/meta, jira/ajs/ajax/ajax-util, jira/util/version, jira/data/parse-options-from-fieldset, jira/ajs/persistence, jira/xsrf, jira/ajs/default-custom-event
jira.webresources:jira-urlhelpers (contains the following AMD-Modules): jira/util/urls
com.atlassian.plugin.jslibs:marionette-1.4.1-factory (contains the following AMD-Modules): atlassian/libs/factories/marionette-1.4.1
com.atlassian.plugin.jslibs:brace-2014.09.03-factory (contains the following AMD-Modules): atlassian/libs/factories/brace-2014.09.03
com.atlassian.plugin.jslibs:skate-0.12.6 (contains the following AMD-Modules): atlassian/libs/skate-0.12.6
com.atlassian.plugin.jslibs:backbone-1.0.0-factory (contains the following AMD-Modules): atlassian/libs/factories/backbone-1.0.0
com.atlassian.plugin.jslibs:underscore-1.4.4 (contains the following AMD-Modules): atlassian/libs/underscore-1.4.4
com.atlassian.auiplugin:aui-form-validation (contains the following AMD-Modules): aui/form-validation, aui/form-validation/validator-register
com.atlassian.auiplugin:aui-inline-dialog2 (contains the following AMD-Modules): aui/inline-dialog2
If you use globals, for example AJS.dialog2, instead of require ('aui/dialog2'), it's a good time to make these changes.
What you need to do
In Jira Service Desk 4.1, your app should work as expected, but you'll need to check your dependencies and take the recommended action outlined below. In 4.2, your app might be impacted by these changes if no action is taken.
Steps to take:
- Check that the dependencies your app needs are specified in your web resources. When checking this, consider if these dependencies are necessary, or if they're negatively impacting load-time performance. You can use https://bitbucket.org/atlassianlabs/atlassian-webresource-webpack-plugin to help achieve this.
- Check that your app works 'as expected' within the new layout. When the service desk admin activates the new layout, the <body> element will contain the class custom-portal-layout-flag.
We'll be releasing an Early Access Program to give you time to test your changes before general release.
If you have a question
You can post any questions to this community page and we'll get back to you as soon as we can.
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.1. For a more tailored upgrade, also check our Pre-upgrade planning tool that will recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.