Jira Service Desk 4.5.x upgrade notes
Below are some important notes on upgrading to Jira Service Desk 4.5. For details on the new features and improvements in this release, see the Jira Service Desk 4.5.x release notes.
Summary of changes
Upgrade notes
We normally do not introduce new features in the Long Term Support release but rather consolidate the ones we've introduced since the last Enterprise releases. See our change log for all the features and fixes between the last LTS releases. Learn more
4.5.9: OAuth 2.0 for incoming mail
This feature was backported from Jira Service Desk 4.10.
Google and Microsoft are planning to deprecate basic authentication. This means that if you’re using one of these email providers (as your mail server in Jira) and create requests or issues via email, you will need to reconfigure your mail servers to use the OAuth 2.0 authentication method instead.
Follow these steps to use OAuth 2.0:
All Jira applications: Integrate Jira with OAuth 2.0. Learn more
Jira Core and Jira Software projects: Reconfigure mail servers to use OAuth 2.0. Learn more
Jira Service Desk projects: Reconfigure email channels to use OAuth 2.0. Learn more
4.5.4: Support for PostgreSQL 10
We've added PostgreSQL 10 to the list of supported platforms. For more info, see Supported platforms.
4.5.4: G1 GC enabled by default for Java 11
If you’re running Jira with Java 11, Garbage First Garbage Collection (G1 GC) will be enabled by default. We’ve already been recommending this method when tuning garbage collection, so now you’ll get it out of the box. G1 GC is more efficient and improves performance, especially in environments with large Java heap.
Java version | Default GC | Recommended GC |
|---|---|---|
| Java 11 | G1 GC |
|
| Java 8 | ParallelGC | ParallelGC |
*Our performance tests have shown that you might benefit from ParallelGC if you have a relatively small Java heap. The difference is not big, but you can consider switching back to ParallelGC if you’re having problems with performance.
4.5.4: Changes in the issue collector
The upcoming update of the Chrome browser introduces new cookie security features, which would essentially break the issue collectors embedded on separate domains. We’ve fixed this problem, but this brought some changes to how issue collectors work:
You can no longer match the submitter’s user session to make them the issue reporter. You can still match them by using their email address.
You don’t have to enable 3rd party cookies to make the issue collector work. We’ve removed this requirement, also dropping some error messages that reminded about it.
The project and issue key will no longer be displayed in the success message after submitting feedback (unless the project is open to Anyone on the web). We did this to improve security by not disclosing information about projects and issues.
For more info on the issue collector, see Using the issue collector.
Increase your pool-max-size before upgrade
If you're upgrading from Jira Service Desk 3.x to 4.x we recommend changing the pool-max-size parameter to 40 in your dbconfig.xml before the upgrade. This prevents re-index ending up with the ResultSet closed error, especially when you use SQL Server or PostgreSQL as your database. For information on implementing the change, see Tuning database connections.
End of support announcements
In Jira Service Desk 4.5, we're making the following changes:
- Advance notice: Deprecating Internet Explorer 11. Jira Service Desk 4.5 will be the last release to support this version of IE. That means that after it reaches "end of life" in 2021, we'll stop all support related to IE 11, and we'll no longer test Jira on IE 11.
For more information, see End of support announcements.
App developers
See Preparing for Jira 8.5 for any important changes regarding apps.
Upgrade procedure
We've prepared a dedicated upgrade guide for upgrading between Enterprise releases. See Long Term Support release upgrade guide.