Learn more about the benefits of upgrading to the latest version.
Jira 8.x から 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.2
OAuth 2.0 の送信メール (SMTP): OAuth 2.0 認証を送信メール サーバーで有効化しました。Google と Microsoft は、SMTP プロトコルとともに、接続のためのプロバイダーとして引き続きサポートされます。
Jira pickers improvements: Instead of initially loading all the available items for a particular picker, we now only display 100 items on the list. This change improves rendering time when creating or editing an issue as well as using Component, Priority, and Version pickers in basic search mode. It also allows you to remain performant at scale even when the number of items to render is growing.
Diagnostic recording configuration with Java Flight Recorder: We’ve added the ability to configure diagnostic recording via the user interface and REST endpoints with Java Flight Recorder (JFR). To get the desired information, you can configure the amount of recorded data to simplify and improve problem diagnostics.
In Jira 9.2, we’ve removed support for MySQL 5.7.
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?
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.
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.
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.
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.
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:
- 画面右上で [管理] > [システム] の順に選択します。
- 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.