Jira Service Desk 4.6.x upgrade notes
Here are some important notes on upgrading to Jira Service Desk 4.6. For details on the new features and improvements in this release, see the Jira Service Desk 4.6.x release notes.
Summary of changes
Upgrade notes
Transferring custom modifications from old Jira files
As you might have read in our release notes, you can now automatically transfer changes from the most important Jira files to your new Jira version. The changes we mean here are connection settings, JVM args, TCP values, and other customizations from files like setenv.sh or server.xml.
- Installer: If you're upgrading with the installation wizard, you should be covered, as you'll be using the same files.
- Tar.gz/zip archive: If you're upgrading manually, you'll be "installing" a new Jira instance next to the existing one. This requires that you copy modifications from old files to the new ones. Now, you can have Jira do this automatically.
When you start your new Jira version, we'll show you the modified files and ask whether you want to transfer them automatically. Feel free to try it out before finding and copying all these changes yourself.
Jira can detect changes in the following files:
<jira-home-directory>/atlassian-jira/<jira-home-directory>/conf/server.xml<jira-home-directory>/bin/setenv.sh
If you've modified other files, you'll need to copy them manually, just like you did before. When in doubt, head to Upgrading Jira applications.
Support for PostgreSQL 10
We’ve added PostgreSQL 10 to our supported platforms. For more info on how to connect Jira to this database, see Connecting Jira to PostgreSQL.
Better support for reply emails from Outlook by mailhandlers
To enable users of Outlook to respond to Jira notifications, we have improved the RegexCommentHandler UI by making it easier to set it up properly, and are advising admins to not use the NonQuotedCommentHandler because it doesn't work with html or rich text emails. This way, admins can set up the handlers in such a way that when users comment in Jira via email, signature text or attachments are removed and not added to the Jira content.
We're also planning on deprecating the ”Add a comment from the non-quoted email body” and ”Create a new issue or add a comment to an existing issue” email handlers in the foreseeable future. For more information, see How to set up replying to Jira notifications via Outlook.
Some apps might not work with new agent queues
We’ve notified app vendors about our changes to agent queues, but it might happen that some apps won’t take these changes into account and break after the upgrade. There’s not too many apps like that, but if you’re having any problems with agent queues in Jira Service Desk 4.6, try disabling apps that use queues in any way.
End of support announcements
In Jira Service Desk 4.6, we’re making the following changes:
End of support: Internet Explorer 11
To allow us to continue to take advantage of modern web standards to deliver improved functionality and the best possible user experience across all of our products, we have decided to end support for Internet Explorer 11.
Advance notice: Several platforms no longer supported in Jira Service Desk 4.8
We're planning to end support for the following platforms in Jira Service Desk 4.8:
Microsoft SQL Server 2012
PostgreSQL 9.4, 9.5
Solaris
Oracle 12c R1
Microsoft SQL Server 2014 (Service Desk 4.10)
MySQL 5.6 (Service Desk 4.10)
For more details, see End of support announcements.
App developers
See Preparing for Jira 8.6 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.6. 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.