Reasons to upgrade

Learn more about the benefits of upgrading to the latest version.

Upgrading from Jira 8.x to Jira 9.x

If you're already on Jira 9.x, feel free to skip this section.

Jira 9.0 is a platform release. As every platform release, it’s brought significant changes that aren’t usually provided in smaller feature releases. All of them affect the upgrade in some way and require that you take extra steps into consideration. Here’s everything you need to know.

Key changes in Jira 9.6

  • Embedded Crowd performance improvements: Crowd membership changes are now batched during full and incremental directory syncs. Also, the requests for DirectoryManager lookups are now cached to boost the efficiency of the feature.

  • Cache App API deprecated: We’ve deprecated the Cache App API endpoint and hidden it behind the com.atlassian.jira.cacheResource dark feature flag, which you can enable. The reason behind this is that the implication the endpoint has on Data Center may be equivalent to a full shutdown. Moreover, there’s no guarantee that an underlying issue will be fixed.
  • jira.diagnostics.ipdlog.poll.seconds system property removed from In-product diagnostics: In the In-product diagnostics tool (IPD), the system property jira.diagnostics.ipdlog.poll.seconds allowed you to change the interval at which the JMX values were polled and written to the log file atlassian-jira-ipd-monitoring.log. The default polling interval was and remains 60 seconds, while the property has been removed from IPD.

Learn more in the release notes

Deciding to upgrade

When deciding to upgrade, you should consider a significant time investment to get new features, performance improvements, bug fixes, continued support access, company requirements, and many other benefits. Here are a few tips on how to prepare for the upgrade.

Upgrade: What am I getting?

New features

  • For every new version of Jira Software, we publish Jira Software release notes and Jira Software upgrade notes. These resources have important information about the upgrade.

  • The upgrade matrix lists all the features and improvements introduced in consecutive Jira releases. The matrix lets you compare versions and select the one you want to upgrade to. It also provides an overview of bugs, fixed in each release.

  • If you want to dig deeper and learn about all the technical specifics of upgrading Jira Software for a particular version, see Technical upgrade notes section in the matrix.

Performance improvements

Many of our releases focus on performance improvements, so you and your team can have an effective product experience with minimal technical slowdown. Two examples of these improvements are the optimization of indexing time and faster page load time for dashboards and issues.

Learn more from the performance report

Bug fixes and new releases

We use the public Jira instance to track the development of product bug fixes and suggestions. Many customers report issues and suggestions that would benefit their team and vote for or watch them. Just like watching Jira issues in your instance, you'll be notified via email when an issue is updated.

View recently resolved issues

View Jira public issue tracker

View the bugfix policy

Access to support

For Long Term Support releases, we provide support and bug fixes in all server products for two years after a version is released. Ending support after two years allows us to focus our resources on supporting more up-to-date versions used by the majority of customers. This means that after a version has reached its end of life, our support team will only be able to assist with upgrade-related questions.

For versions that aren’t Long Term Support releases, we provide support for two years but the fixes are available only until the next version is out. Then, we only fix critical bugs. If you want to get all the new features and fixes, it's good to upgrade versions.

View the End of life policy

Upgrade: what should I consider?

In addition to technical considerations, there are a few other factors to consider for a smooth upgrade.


The amount of time for the upgrade depends on several factors, including the size of your instance and the number of apps and customizations. As a general rule, it's best to incorporate some buffer time for planning and execution in case anything unexpected comes up.


No external tools are required to complete the Jira upgrade. There are a few handy resources that can help you along the way, like the App Compatibility Checker and the Instance Health Check.

To open these Jira tools:

  1. In the upper-right corner of the screen, select Administration  > System.
  2. In the left panel, go to System support and select Troubleshooting and support tools. 


It's a good idea to carefully consider how to communicate information about the upgrade, especially if it’s introducing major changes. You might consider informing an approver, end users, and, if you've acquired the license through an approved Atlassian Solution Partner, your partners, as they may offer additional services to assist you during the upgrade.

All ready?

Head back to the upgrade matrix, and choose the version you want to upgrade to.

Go to the upgrade matrix

Last modified on Jan 24, 2023

Was this helpful?

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