Jira Software 9.1.x release notes

Still need help?

The Atlassian Community is here for you.

Ask the community

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.

Learn more about how to handle full reindex and estimate downtime

Known issue: Can’t edit priorities in admin panel 

We’ve discovered an issue in 9.1 release: editing a priority in the admin panel results in 500 Internal Server Error. This issue will be fixed in the next bugfix release: Jira 9.1.1.

While we’re working on it, you can track the resolution progress and learn more about the problem in this ticket: JRASERVER-74138 - Getting issue details... STATUS

We want you to be aware of this issue, so you can work around it, if needed. We’ll update this note once we release the fix.


Read the upgrade notes for important info about this release and see the full list of issues resolved.

 Compatible applications

If you're looking for compatible Jira applications, look no further:

Good to know

If you're thinking of moving to Data Center, check our recommendations first. See: Infrastructure recommendations for Jira.

Performance improvements for Agile boards

Working with numerous sprints simultaneously in Jira could be a bit of a challenge: the more sprints there are in Jira, the slower Agile boards would become. This results in delayed Backlog view loading or slow response when modifying sprints in boards. Since this release, this is no longer the case.

We’ve improved the way how Jira handles Agile boards and loads sprints. Such actions as opening an Agile board and modifying sprints are now completed much faster so you can focus on work without being interrupted by performance issues.

You can find more information about the problem we’re fixing in this ticket: JSWSERVER-20618 - Getting issue details... STATUS

For the implementation details, check out the notes.

Exclude events from the audit log DATA CENTER

We've added new functionality that allows excluding some audit events from being recorded in the log. The new feature is available for admins on the Audit log settings page under the System support section (in the left-side panel):

  1. Audit log: Here, you can view all events recorded in the log.
  2. Settings: A tab where all the audit log settings are configured.

You can view and add the events by scrolling down to the bottom of the page:

  1. Excluded events: this is where admins can block events from being recorded.

To access the feature, you must have Jira System admin permissions.

Diagnose and troubleshoot Jira on the fly with Java Flight Recorder

Accurately diagnosing and troubleshooting problems with Java apps can be a tough task that requires digging through gigabytes of logs to figure out what exactly went wrong. Jira 9.1 supercharges your ability to identify and resolve problems as they occur by bundling Jira with the Java Flight Recorder, a lightweight diagnostic tool for analyzing and troubleshooting apps at runtime.

As the Java Flight Recorder is now managed through Jira, you no longer need to upgrade Atlassian Troubleshooting and Support Tools yourself to start collecting runtime data — continuous runtime data recording is now done automatically.

To learn more about the feature:

Additionally, if you’d like to have a go at resolving the issue yourself or just take a look at what’s been collected, use the JDK Mission Control app to see everything at a glance.

Prioritized search results in the issue navigator

To address the problem of searching through too many custom fields for those users who have plenty of fields in Jira, we’ve added a results prioritization feature in the Columns dropdown of the Issue search view in the List mode.

Now, even when a searched query matches multiple fields, the exact matches will be displayed first. So, it will be easier for you to find and select the needed field, even with the limitation to the displayed number of results.

Keep your site running like clockwork with app monitoring

Keeping a big, busy site running smoothly requires a well-thought-out monitoring strategy. Many of you already use JMX to monitor things such as memory usage and CPU utilization. Now you can turn on application monitoring to get an even more granular view from the new app-specific metrics.

The monitoring screen allows you to turn JMX and app monitoring on or off as needed. 

Learn how to monitor application performance

Diagnose performance problems

Investigating the cause of performance issues can be tricky, especially if you have many Marketplace or custom-built apps. It can be hard to know if the problem is the application, an installed app, or a misconfigured integration.

App-specific metrics include the plugin key, to give you a clearer picture of exactly what your apps are doing. This helps you rule out or pinpoint the source of a problem faster. 

Spot issues before they happen

One of the biggest benefits of monitoring is the ability to be alerted to potential problems before they happen. We know from our own monitoring of huge Jira sites that identifying problems early is essential to maintaining uptime and a good user experience.

Some of the things you can now monitor include how long it's taking to render web panels, perform database operations, indexing, and more.

See the full list of app metrics and suggested alerts 

Performance monitoring dashboards to get you started

If you don't currently have any monitoring, now is a great time to consider it. We've created some Grafana templates that you can use out-of-the box, or as a jumping-off point, to build your own dashboards.

Grafana dashboards to get you started with monitoring

Learn how to monitor Jira with Prometheus and Grafana

Improved indexing management at Jira start-up DATA CENTER

With every new release, we’re aiming to improve Jira’s performance to power your productivity in the application. As more and more users rely on Jira and its scaling capabilities, ensuring better performance at increased scale becomes crucial.

In Jira 9.1., we’ve made the start-up procedure much more resilient. Now, when you’re starting multiple nodes, Jira will ensure that each of them ends up with a healthy index. If you’d like to know more about the changes, check out Changes to index management on the Jira startup in version 9.1.

Resolved issues

Last modified on Dec 7, 2022

Was this helpful?

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