Jira Core 9.2.x リリース ノート

Jira Core リリース ノート

このページの内容

このセクションの項目

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

8.x から 9.x へのアップグレードでは Jira の完全な再インデックスがトリガーされるため、プロセス中にダウンタイムが発生します。現在 8.x をご利用の場合、ダウンタイムを予測したうえでアップグレードに最適な時間枠を選ぶようにしてください。

完全な再インデックスやダウンタイムの予測方法の詳細の確認

 さらに読む

本リリースに関する重要な情報をアップグレード ノートで確認し、解決済みの課題の完全な一覧をご確認ください。

 互換性のあるアプリケーション

互換性のある Jira アプリケーションをお探しの場合、次のページをご参照ください。

 考慮事項

Data Center への移行をご検討の場合、弊社の推奨事項をご参照ください。「Jira のインフラストラクチャの推奨事項

Jira Agile ビュー: 読み込みが速くパフォーマンスが向上

We've always been laser-focused on Jira performance improvements and this release comes with yet another update. This time, we've optimized page load times for Jira Backlog and Board agile views.

As the app gets faster and more reliable, you can get more out of your work in Jira, specifically if you're dealing with slow-performant hardware or network issues. This change is just a part of our planned performance enhancements so expect more to come in the upcoming releases.

Interested in technical details behind this update? We have it covered in the Preparing for Jira 9.2 notes, just take a minute to check it out.

送信メールに OAuth 2.0 を導入

OAuth 2.0 認証を送信メール サーバーで有効化しました。Google と Microsoft は、SMTP プロトコルとともに、接続のためのプロバイダーとして引き続きサポートされます。今後は、送受信の両メール サーバーで OAuth 2.0 を使用するようにセットアップできます。これによって、Jira 統合やサードパーティ アプリとの接続において厳重なセキュリティを提供します。

送信メールの設定では、プロバイダーに応じて利用可能な認証方法を選択するか、JNDI ロケーションの使用を有効化できます。設定の準備ができたら、変更を適用する前に接続をテストできます。

The feature is active by default. But if needed, you can continue using your current outgoing mail configuration.

Learn more about SMTP mail server configuration

Jira Picker のパフォーマンスが大幅に向上

Ready for another portion of performance-related changes? Meet one more set of improvements in Jira pickers.

Further to project picker updates introduced in Jira 8.21, we’ve optimized a few more dropdown menus in the app: ComponentPriority, and Version pickers in the basic search mode. More than that, working with pickers when creating or editing an issue got much faster as well. You can now be sure that your app performance won’t be affected by a growing number of elements to render.

Wondering what’s changed in particular?

We’ve revamped the way search results are rendered: instead of initially loading all the available items for a particular picker, we now only display 100 items on the list. We query the backend as you type, returning exactly what you’re looking for.

You can also use newly added API endpoints to query versions, components, issue types, resolutions, statuses, and priorities. These endpoints return paginated results to limit the response size of potentially large collections of items.

/api/2/status/page

パラメーター

名前

タイプ

Is mandatory?

説明

query

string

OPTIONAL

A sequence of characters expected to be found in status names. When no value is provided, all statuses will be returned.

startAt

long

OPTIONAL

Indicates which status should be used as the first item in the page of results. The default value is 0.

maxResults

int

OPTIONAL

Indicates how many statuses will return per page. The default value is 100.

issueTypeIds

string

OPTIONAL

A list of issue type IDs to further restrict the search. When provided, only statuses available in given issue types will be returned.

projectIds

long

OPTIONAL

A list of project IDs to further restrict the search. When provided, only statuses available in given projects will be returned.

Sample request

GET http://<sample instance>/rest/api/2/status/page?query=Do

応答の例 

/api/2/component/page

パラメーター

名前

タイプ

Is mandatory?

説明

query

string

OPTIONAL

A sequence of characters expected to be found in component names. When no value is provided, all components will be returned.

startAt

long

OPTIONAL

Indicates which component should be used as the first item in the page of results. The default value is 0.

maxResults

int

OPTIONAL

Indicates how many components will return per page. The default value is 100.

projectIds

long

OPTIONAL

A list of project IDs to further restrict the search. When provided, only components available in given projects will be returned.

/api/2/issuetype/page

パラメーター

名前

タイプ

Is mandatory?

説明

query

string

OPTIONAL

A sequence of characters expected to be found in issue type names. When no value is provided, all issue types will be returned.

startAt

long

OPTIONAL

Indicates which issue type should be used as the first item in the page of results. The default value is 0.

maxResults

int

OPTIONAL

Indicates how many issue types will return per page. The default value is 100.

projectIds

long

OPTIONAL

A list of project IDs to further restrict the search. When provided, only issue types available in given projects will be returned.

/api/2/resolution/page

パラメーター

名前

タイプ

Is mandatory?

説明

query

string

OPTIONAL

A sequence of characters expected to be found in issue resolution names. When no value is provided, all issue types will be returned.

startAt

long

OPTIONAL

Indicates which resolution should be used as the first item in the page of results. The default value is 0.

maxResults

int

OPTIONAL

Indicates how many issue resolution will return per page. The default value is 100.

/api/2/priority/page

パラメーター

名前

タイプ

Is mandatory?

説明

query

string

OPTIONAL

A sequence of characters expected to be found in priorities names. When no value is provided, all issue types will be returned.

startAt

long

OPTIONAL

Indicates which priorities should be used as the first item in the page of results. The default value is 0.

maxResults

int

OPTIONAL

Indicates how many priorities will return per page. The default value is 100.

projectIds

long

OPTIONAL

A list of project IDs to further restrict the search. When provided, only priorities available in given projects will be returned.

/api/2/version

パラメーター

名前

タイプ

Is mandatory?

説明

query

string

OPTIONAL

A sequence of characters expected to be found in version names. When no value is provided, all issue types will be returned.

startAt

long

OPTIONAL

Indicates which version should be used as the first item in the page of results. The default value is 0.

maxResults

int

OPTIONAL

Indicates how many versions will return per page. The default value is 100.

projectIds

long

OPTIONAL

A list of project IDs to further restrict the search. When provided, only versions available in given projects will be returned.

JFR の診断記録設定

JFR (Java Flight Recorder) によって、診断記録をユーザー インターフェイスと REST エンドポイントから設定できる機能を追加しました。これで、必要な情報を取得する目的で、問題の診断を簡素化して改善するために記録されるデータの量を設定できます。

To do this, you can adjust the following JFR settings:

  • Maximum recording age
  • Maximum recording size
  • Thread dumps recording interval

By playing with these settings, you get the power to boost troubleshooting on your instance and, as a result, fix problems faster and more effectively.

Learn more about how to use Java Flight Recorder


解決済みの課題

9.2.0 で解決された課題

Released on  

T キー 要約 ステータス
Loading...
Refresh

最終更新日: 2022 年 10 月 24 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する

このセクションの項目

Powered by Confluence and Scroll Viewport.