This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 8.1. 

すべての変更と EAP

ここでは、変更の概要と、それらが実装されている EAP 単位での変更の詳細情報を案内します。

変更の概要

In this section we'll provide an overview of the changes we intend to make in Jira 8.1, 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. 

Deprecating 32-bit installers

Status: PLANNED

We are considering only providing 64-bit installers for Jira, and deprecating the 32-bit ones. Users who need to stay on 32-bit systems will be able to install Jira by using the zip/tar.gz archives. The 32-bit installers will not be removed in Jira 8.1, but they might be deprecated in this version, and then removed in Jira 8.2.

Batched email notifications: improvements

Status: PLANNED

We'll be improving batched email notifications by removing a limitation that didn't allow to use custom fields in emails. Custom fields will be supported, but we'll still keep this feature disabled by default. This will probably change in the next releases, as we want notifications to be batched by default eventually.

'Issue details' panel is resizable on Scrum/Kanban boards

ステータス: 実装済み (詳細については EAP 1 を参照)

Until now, users could manually resize the 'Issue details' panel only on Scrum/Kanban backlogs (you can check how it works there). After receiving many requests, we've also added this possibility to Scrum/Kanban boards. Additionally, we've added a horizontal scrollbar for boards that have many columns and are displayed on small screens.

Column headers limited to 1 line

ステータス: 実装済み (詳細については EAP 1 を参照)

This change was released in Jira 8.0.2, just making sure you know about it. 

Column headers will be limited to one line, containing the column name (shortened with ellipsis), and column constraints (min. and max. issues, if enabled). For details, see EAP 1.

新しいアバター

ステータス: 実装済み (詳細については EAP 1 を参照)

This change was released in Jira 8.0.2, just making sure you know about it. 

We're updating project and users avatars with new colors and shapes. For details, see EAP 1.

Lazy-load to improve performance

ステータス: 実装済み (詳細については EAP 1 を参照)

We've introduced lazy loading of card colors and boards in the board picker to improve the overall loading time. 

Issue archiving for early adopters

ステータス: 実装済み (詳細については EAP 1 を参照)

To help keep Jira clean and clutter-free, we've introduced the option to archive individual issues. 

New events for issue archiving

ステータス: 実装済み (詳細については EAP 1 を参照)

We've added two new events related to issue archiving: Issue Archived and Issue Restored.

Component archiving

ステータス: 実装済み (詳細については EAP 1 を参照)

You can now archive components so that they can't be selected and linked to issues and are marked as 'Archived'.

変更の実装内容

In this section we'll provide details of changes we have implemented, organized by the EAP they are first available in. 

このマイルストーンでの変更

このマイルストーンには大きな変更はありません。

このマイルストーンでの変更

Lazy loading of card colors and boards in board picker

To make your issues more visible and recognizable on boards and backlogs, you can assign card colors to issue types. However now, we've changed the way those colors are loaded. Introducing lazy loading does not change how the feature works but results in faster boards and backlogs.

Board picker helps you quickly navigate through boards. To optimize response time, we've decided to change the way we load boards for the board picker. Now we load the boards only when you interact with the picker icon, which saves Jira a lot of hassle. In this way, even though we leave the functionality intact, we offer you a faster loading solution.

'Issue details' panel is resizable on Scrum/Kanban boards

Until now, users could manually resize the 'Issue details' panel only on Scrum/Kanban backlogs (you can check how it works there). After receiving many requests, we've also added this possibility to Scrum/Kanban boards. Additionally, we've added a horizontal scrollbar for boards that have many columns and are displayed on small screens.

Column headers limited to 1 line

列見出しは 1 行に制限され、列名 (省略記号で省略) および列の制約 (有効化されている場合は最小および最大課題件数) が含まれます。

新しいアバター

プロジェクトおよびユーザー アバターを更新しています。

ユーザーのアバター

• デザイン ガイドラインに合わせて色を更新しています。

プロジェクトのアバター

• 円形のアバターから角丸のアバターに切り替えています。
• デザイン ガイドラインに合わせて色を更新しています。
  
  

Issue archiving for early adopters

Issues can either be archived one by one or in bulk. Once an issue is archived it is removed from the index and disappears from the search results, dashboard, boards, and backlogs. 

If needed, individual issues can be restored with a direct link. 

The feature is available both using the UI or the REST API. 

Currently, the scope of archiving and restoring issues is limited due to the feature being in an early stage of development. 

New events for issue archiving

We’ve added two new events related to issue archiving that you can use in your notification schemes:

• Issue Archived: notifies you whenever an issue is archived.
• Issue Restored: notifies you whenever an issue is restored.

Component archiving

You can now archive components so that they do not clutter your Jira instance. Archived components still show on the components list but are marked as 'Archived' and they cannot be selected in the Component/s dropdown. 

The feature is not yet available in Jira Service Desk. We'll add support for Service Desk in the next releases.