Jira 8.21 への準備
This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.21
概要
最新バージョン
ここでは最新の EAP についての情報をご案内します。
アプリケーション / 日付 | EAP 番号 | バージョン (Maven) | ダウンロード |
|---|---|---|---|
Jira Core/Software | 8.21.0-rc01 | 8.21.0-m0002 | Source files (Core) Source files (Software) |
Jira Service Management
| 4.21.0-rc01 | 4.21.0-m0002 |
変更の概要
In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your apps. Once they're ready, we'll indicate when a change has been implemented, and in which milestone.
Project Picker Improvement
Status: IMPLEMENTED (eap 01)
So far the project picker search has been done in the browser rather than on the server side. This means each time all the projects were displayed in a drop-down list while loading a page. A growing number of projects on the Jira instance and increasing rendering time slows the search down.
The new approach improves the behavior by querying the backend with the given phrase. Jira returns only matching elements. Empty queries or whitespaces are ignored.
Changes and additions to the API
In order to speed-up the search, we're exposing a new project picker search endpoint /api/2/projects/picker that will allow the project pickers to fetch the available projects that match a user query.
The project picker endpoint won't return any results if the query is empty. The results will have a special html field with the query highlighted to easily show display it in the browser.
パラメーター
| 名前 | タイプ | Is mandatory? | 説明 |
|---|---|---|---|
query | text | 任意 | It’s a sequence of characters expected to be found in the word-prefix of project name and/or a key. If blank or missing, empty array of project is returned. |
Sample request
GET http://<sample instance>/jira/rest/api/2/projects/picker?query=a
応答の例
Language support for Advanced Roadmaps
Status: IMPLEMENTED (eap 01)
We will be adding support for the following languages in Advanced Roadmaps:
- zh_CN - 中文 (中国)
- cs_CZ - čeština (Česko)
- da_DK - dansk (Danmark)
- nl_NL - Nederlands (Nederland)
- en_UK - English (UK)
- et_EE - eesti (Eesti)
- fi_FI - suomi (Suomi)
- fr_FR - français (France)
- de_DE - Deutsch (Deutschland)
- hu_HU - magyar (Magyarország)
- is_IS - íslenska (Ísland)
- it_IT - italiano (Italia)
- no_NO - norsk (Norge)
- ja_JP - 日本語 (日本)
- ko_KR - 한국어 (대한민국)
- pl_PL - polski (Polska)
- pt_BR - português (Brasil)
- ro_RO - română (România)
- ru_RU - русский (Россия)
- sk_SK - slovenčina (Slovensko)
- es_ES - español (España)
- sv_SE - svenska (Sverige)
Comment emoji reactions (Data Center)
App: JIRA SERVICE MANAGEMENT
Status: IMPLEMENTED (eap 01)
Following in the footsteps of Jira, we’re bringing comment reactions to Jira Service Management. Emojis are there to speed up the communication process in requests and the customer portal. We’ve also improved the accessibility of the comment section navigation.
Requests view configuration (Data Center)
App: JIRA SERVICE MANAGEMENT
Status: IMPLEMENTED (eap 01)
You can now customize the requests list view as an admin to select exactly which columns the users will have access to. Then, the users can pick and choose between the columns they find useful and even rearrange them.
Improved background events processor
App: JIRA SERVICE MANAGEMENT
Status: IMPLEMENTED (eap 01)
Jira Service Management’s background processor is responsible for processing Jira events and executing JSM automations, notifications, and calculating complex values like SLAs in the background. In 4.21.0 we're enabling a new improved implementation of our processor that’s more resilient and cluster-efficient. This processor has been available in Jira Service Management since 4.9.0 as an experimental feature, and after much testing and stabilization, we're now releasing it as the default processor.