Jira Core 8.7.x アップグレード ノート
Here are some important notes on upgrading to Jira Core 8.7.
For details on the new features and improvements in this release, see the Jira Core 8.7.x release notes.
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.
カスタム フィールドの説明における HTML の無効化
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.
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.
To enable G1 GC, we’ve changed the
set-gc-params.sh/bat file. If, for any reason, you need to switch to a different garbage collector, you can do so by modifying this file.
PostgreSQL 11 のサポート
サポート対象プラットフォームに PostgreSQL 11 を追加しました。
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.
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.
Jira バージョン 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.