Jira Software 8.7.x upgrade notes
Here are some important notes on upgrading to Jira Software 8.7.
For details on the new features and improvements in this release, see the Jira Software 8.7.x release notes.
Fetching updates to be fixed for Jira in version 8.7.2
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.7.2. Make sure you upgrade to this version for Jira to update without further issues.
Increase pool-max-size on upgrade
If you're upgrading from Jira 7.x to Jira 8.x we recommend changing the pool-max-size parameter to 40 in your dbconfig.xml before the upgrade. Leaving the default of 20 can sometimes lead to “ResultSet Closed” errors during re-indexing on 8.x. For information on implementing the change, see Tuning database connections.
Disabling HTML in custom fields description
With Jira 8.7.0, we’re changing the default behavior of the Enable HTML in custom field descriptions and list values items option. It will now be switched to OFF for new Jira installations and the upgraded ones that have never used it.
If you have modified this option, you shouldn’t be affected, but do we recommend that you check the it to make sure it's set correctly for your instance. You can find it by going to> System > General configuration.
We recommend that you keep this option disabled for security reasons.
PostgreSQL 11 support
We’re adding PostgreSQL 11 to our supported platforms for Jira Server and Data Center and Aurora PostgreSQL 11.4 for Jira Data Center.
OpenID Connect support DATA CENTER
Many enterprises still struggle to use industry-standard user management tools to authenticate to Atlassian. Way back we added SAML support to all of our Data Center products and now we are adding a new authentication option through OpenID Connect integration to enable seamless integration with 3rd party Identity Providers.
For more information, see OpenID Connect.
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.
End of support announcements
In Jira 8.7, we haven't made any changes to what Jira supports.
For more details, see End of support announcements.
See Preparing for Jira 8.7 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. For a more tailored upgrade, go to > Applications > Plan your upgrade. We’ll recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.