Jira Core 8.14.x upgrade notes
Here are some important notes on upgrading to Jira Core 8.14.
For details on the new features and improvements in this release, see the Jira Core 8.14.x release notes.
Changes in startup files
We've changed several startup files to change the format of GC logs produced by Jira while running with Java 11. Without the change, the logs are impossible to parse with the GCViewer tool and can be frustrating for an admin to work with.
We've changed the
tags,time,uptime,level in the following files:
bin/set-gc-params.shfile on Linux
bin/set-gc-params.batfile on Windows
bin/set-gc-params-service.batfile on Windows
If you don't have any custom changes in those files, you don't need to take any cation. If you do, you'll need to copy your changes to the new files on upgrade.
Change in logging in with passing credentials in URL parameters
Since the credentials might end up as a plain text entry in different log files (such as that of load balancers or proxies), this method poses a security risk. To mitigate it, we want to block its default availability, and make it an option only in special cases. We’ll also sanitize the access logs of the Tomcat web server bundled with Jira.
However, for the internal and legacy integrations to keep working, we still want to provide a way to use this method. You’ll have to set the special system property
true. That way your legacy and/or internal integrations will still work. To keep your logs under control, it’s also a good idea to review your logs for possible credential entries.
End of support announcements
There are no changes in this release. For details on what's supported, see Supported platforms.
See Preparing for Jira 8.14 for any important changes regarding apps.
Upgrading from a Jira version 8.x.x?
See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps.