Jira Software 9.10.x upgrade notes
Here are some important notes on upgrading to Jira Software 9.10.x.
Upgrading from 8.x to 9.x triggers full Jira reindex that causes some downtime during the process. If you’re on 8.x now, make sure you’ve estimated the downtime and set the best time for the upgrade.
If you’re upgrading to Jira Software 9.10, we recommend that you also upgrade the New Relic agent to version 8.2.0. Learn more in the New Relic agent release notes
Jira Software 9.10 is using Apache Tomcat 9.0.75, which isn’t compatible with earlier versions of the New Relic agent. This incompatibility might cause issues when Jira is started in the browser.
Search for projects and issue types in custom field contexts
The UI for this feature is still a work in progress and to offer the best possible user experience, it is not currently available by default. To access the new functionality, turn on the
jira.customfields.configure.modern.ui feature flag.
On large instances with custom fields reused across numerous projects, finding the needed field contexts can take some time. Especially if you want to add or remove an issue type or project from the context, but don’t know exactly where they appear. To make this process more efficient, we’ve introduced the Projects and Issue types menus.
When you select a particular item in a menu, you’ll see the list of contexts it appears in. Keep in mind that the same project can’t appear in more than one context, per custom field. Learn more about configuring contexts for custom fields
A custom field context that matches two projects selected in the Projects menu
Two custom field contexts that match issue types selected in the Issue types menu
The information in the Contexts table might vary depending on the field type.
Such columns as Context, Issue types, Projects, and Actions are always displayed for any custom field. However, if your field has specific customization or multiple properties, such information will be added as extra columns to the table.
Get notified about Jira reindexing only when it’s really required DATA CENTER
A message about the required reindex will no longer pop up after you simply restart Jira. The message will appear only after you make major configuration changes in your instance. For example, after you add a custom field or change the time tracking settings. Learn more about Jira re-index after different instance configurations
We made some investigation to find out why the message about the required reindex appeared after the Jira restart. We discovered that after the restart, the plugins using custom fields got enabled automatically and triggered the message when the reindex wasn’t needed.
We’ve fixed this behavior to inform you about the reindex only when it’s really required and to strengthen your confidence in administrative operations in Jira.
Obfuscate the plain text password in server.xml for Tomcat DATA CENTER
As a Jira administrator, you can now obfuscate the plain text password used in the server.xml file for Tomcat by using Jira’s out-of-the-box password cipher method – basic encryption with Base64Cipher. Using the plain text password as is might be unsafe and introduce vulnerabilities to the system.
In Jira 9.10, we’re adding support for:
- PostgreSQL 15
- SQL Server 2022
See Preparing for Jira 9.10 for any important changes regarding apps.
Upgrading from a Jira version 9.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 Jira administration > 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.