Jira Software 8.5.x upgrade notes

Jira Software release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Here are some important notes on upgrading to Jira Software 8.5.

For details on the new features and improvements in this release, see the Jira Software 8.5.x release notes


 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 Long Term Support releases (Jira 7.6 and Jira 7.13). See our change log for all the features and fixes between the last LTSs. Learn more

If you use our REST API, make sure to look up our REST API change log for an overview of changes. 

8.5.4: Support for PostgreSQL 10

We've added PostgreSQL 10 to the list of supported platforms. For more info, see Supported platforms.

8.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 11G1 GC
  • G1 GC for large Java heap
  • ParallelGC for small Java heap*
Java 8ParallelGCParallelGC

*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.

How do I change the GC method?

To change the default GC method:

  1. Stop Jira.

  2. Edit the setenv.sh/.bat file, and search for JVM_GC_ARGS. You’ll find available parameters described inside.

  3. If you’re running Jira as a service on Windows, you’ll also need to modify the gc-params-service.bat file.

8.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.

8.5.5: New API to help the Versions view load faster

To help the Versions view in project settings load faster and avoid possible timeouts on large instances, we have changed the endpoint it called. 

Now, instead of .../release/allversions we use GET /rest/projects/1.0/project/<project_key>/release/allversions-nodetails to return the list of all project versions together with their data such as their name, status, or description (except the progress data). Archived versions are also returned. 

We also changed the way the information about the number of issues in each status category (To do, In progress, Done) related to each version is returned. This data, collectively known as Progress, is now lazy-loaded as the page is scrolled and uses a separate new endpoint. 

The old endpoint is still working however, is not used by the releases after and including Jira 7.13. 

New endpointData it retrieves

GET

/rest/projects/1.0/project/<project_key>/release/allversions-nodetails

List of project versions and their data
POST /rest/projects/1.0/project/<project_key>/release/details/progressProgress for each version

This is not a breaking change. 

Fetching updates to be fixed for Jira in version 8.5.7

If you use Jira with other Atlassian products such as Bamboo, Bitbucket or Fisheye/Crucible, you might have experienced it getting stuck paging over issue updates. This happens when the collective number of results to fetch is bigger than 50. We have worked on a fix and will bundle it in Jira version 8.5.7. Make sure you upgrade to this version for Jira to update without further issues.

Displaying statuses and loading versions to be fixed in Jira 8.5.7

We've implemented a fix to help all project versions load properly in the Versions panel even if the number of versions is large. Additionally, we solved the problem of statuses not displaying properly on the Sprint report. 

 End of support announcements

In Jira 8.5, we're making the following changes:

  • Advance notice: end of support for 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. 

    Jira 8.5 will be the last version to support Internet Explorer. 

    See End of support announcements for full details. 

 App developers

See Preparing for Jira 8.5 for any important changes regarding apps.

 Upgrade procedure

Upgrading from a previous Long Term Support release?

See our dedicated upgrade guide

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.

Last modified on Jul 16, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.