このドキュメンテーションは、既存のアプリと Jira Software Data Center 11.2、Jira Service Management Data Center 11.2 との互換性を確認したい Jira 開発者向けです。

最新バージョン

ここでは最新の EAP についての情報をご案内します。

変更の概要

このセクションでは、導入予定の変更の概要を紹介します。アプリへの影響の検討にお役立てください。アップデートの準備が整ったら、実装のタイミングとマイルストーンが表示されます。

• Jira Software と Jira Service Management の共通機能
  • サポート対象プラットフォームの変更
  • Welcome OpenSearch in Jira Data Center
  • Indexing and snapshots improved with OpenSearch
  • Implement custom query mappers for your app
  • OAuth 2.0 でアプリ リンクを安全に接続する
  • Protect your Jira nodes with JQL resilience
  • Strengthen sysadmin and OS access separation 
  • Optimize your instance with safeguards 
  • One place to clean them all 
    
• Jira Software の機能
  
  • Deprecation of Browse Project properties in workflows
  • New limit of 10,000 items on a board 
  • Jira Mobile plugin removal
• Jira Service Management の機能
  
  • New REST API scopes for service accounts
  • Link your Jira with Confluence through OAuth 2.0

Jira Software と Jira Service Management の共通機能

サポート対象プラットフォームの変更

ステータス: 実装済み (EAP 01)

In Jira 11.2, support for Microsoft SQL Server 2019 (MSSQL 2019) is deprecated.

Welcome OpenSearch in Jira Data Center

ステータス: 一部実装済み (EAP 01)

With the Jira Data Center 11.2 release, OpenSearch will be fully supported for production use. You can now configure Jira to use OpenSearch as your search platform, either on premises or as a managed service like AWS OpenSearch Service. Explore how to configure OpenSearch for Jira

We recommend switching to OpenSearch because it offers performance, scalability, and reliability improvements over Lucene.

To understand the differences between OpenSearch and the default Lucene search platform, review the OpenSearch for Confluence Data Center guide. While this guide focuses on Confluence, the information about the search platforms is also relevant for Jira. We're working on a Jira-specific report and will share it as soon as it's ready.

You might also want to get familiar with our previous OpenSearch documentation:

• Jira 11 の検索 API の非推奨機能およびアップグレード ガイド
• Jira 11 で FieldIndexer を移行する
• Lucene Collectors を Jira 11 の検索 API に移行する

Indexing and snapshots improved with OpenSearch

ステータス: 実装済み (EAP 01)

When OpenSearch is enabled in Jira Data Center, you’ll notice changes to both the user interface and REST APIs. The Index Admin UI now uses a new URL (OpenSearchIndexAdmin.jspa) and offers a different set of configuration options tailored for OpenSearch.

The indexing and snapshot API endpoints now reflect OpenSearch-specific behavior.

• The reindex endpoint always performs a full background reindex:
  • /jira/rest/api/2/reindex
• The snapshot endpoints are disabled because they don’t apply to OpenSearch:
  • /rest/api/2/index-snapshot
  • /rest/api/2/cluster/index-snapshot/{nodeId}

Implement custom query mappers for your app

Status: IMPLEMENTED (EAP 01)

You can now extend your app to support custom search operations across both Lucene and OpenSearch backends. If your app needs to translate custom query objects into search engine queries, you’ll need to implement custom query mappers for each backend.

Explore how to implement custom query mappers

OAuth 2.0 でアプリ リンクを安全に接続する

Status: IMPLEMENTED (EAP 01)

Atlassian Data Center 製品全体で、アプリケーション リンク (アプリ リンク) の OAuth 2.0 サポートを導入します。OAuth 2.0 は、アトラシアン製品と外部アプリ間において、安全かつ最新であり、信頼性の高い接続を可能にする、業界標準の認証プロトコルです。

アトラシアンは、ハイブリッド環境での安全かつ効率的な統合を可能にする、クラウドに接続するための OAuth 2.0 ベースのアプリ リンクにも取り組んでいます。タイムラインは近日公開予定です。

Protect your Jira nodes with JQL resilience

Status: IMPLEMENTED (EAP 01)

We’re introducing JQL resilience, a set of safeguards that help prevent node crashes caused by resource-intensive JQL operations. To stop a JQL query from using too much memory or running for too long, you can:

• set a maximum search result limit.
• define a JQL query time limit to interrupt queries that run too long.
• enable a memory usage circuit breaker to reject new JQL queries when memory is low.

For each node, you can control these limits in the jira-config.properties file. Each change requires you to restart Jira for it to take effect.

Strengthen sysadmin and OS access separation

Status: BREAKING CHANGE PARTIALLY IMPLEMENTED (EAP 01)

We’re improving Jira Data Center security by further separating product sysadmin and operating system (OS) access. This change doesn’t affect Jira Software features. In Jira Service Management, we’ve secured the Groovy Console behind the system property assets.groovy.console.enabled and added audit logging.

We’ve clarified the distinction between the global administrative permissions: Jira Administrator and Jira System Administrator. Access to sensitive features in Jira has been refined to ensure that only the appropriate roles have the required permissions.

To help you manage this transition, we've introduced a new application property: jira.strict.admin.permissions. This property lets you opt in to the updated role requirements at your own pace. It controls the following features:

• Some feature flags now require the Jira System Administrator role.
• Changing Java Management Extensions (JMX) settings now requires the Jira System Administrator role.

System administrators can update this property in the jira-config.properties file or in the advanced settings in Jira. By default, this property is set to false. This means the stricter permissions are opt-in for now, but they'll become opt-out in a future major version of Jira Data Center.

Optimize your instance with safeguards

Status: IMPLEMENTED (EAP 01)

Jira Instance Optimiser now includes safeguards to help you stay within recommended limits for comments, custom fields, issue types, issues, and projects. These safeguards help maintain system stability and performance as your instance grows.

To set up the limits:

1. Jira アプリケーションの右上隅で [Jira 管理] > [システム] の順に選択します。
2. サイドバーで、[インスタンス最適化ツール] を探し、[概要] を選択します。
3. Select Configure safeguards.

You can enable or disable safeguard enforcement, and choose whether to receive email and in-app notifications. When usage approaches a set limit, system admins receive notifications. If a user tries to perform an action that would breach a safeguard, the action is blocked and the user receives a warning. 

More about Instance Optimizer for Jira

One place to clean them all 

Status: IMPLEMENTED (EAP 01)

We're deprecating the Clean up functionality in Jira Data Center and removing the Audit Custom Fields link. Instead, the cleanup features, such as project and issue archiving, are now integrated into the preinstalled Instance Optimizer app, which provides more efficient and automated ways to optimize your instance.

With this change, you’ll find all the cleanup features in one place. More about Instance Optimizer for Jira

Jira Software の機能

Deprecation of Browse Project properties in workflows

ステータス: 実装済み (EAP 01)

Starting in Jira 11.2.0, we're deprecating the jira.permission.browse.* workflow step properties.

You can enable the com.atlassian.jira.workflow.permission.browse.removal feature flag to preview the removal enforcement.

Jira permission manager will ignore these Browse Project properties starting from version 12.0.0. To prepare for this change, you’ll need to update your workflows to use alternative such as security levels and Automation for Jira (A4J).

New limit of 10,000 items on a board

ステータス: 実装済み (EAP 01)

With the OpenSearch implementation in Jira, Scrum and Kanban boards can display up to 10,000 items. When a board is full, an admin needs to update the board filter to reduce the number of included issues. This update helps Jira scale for large enterprises, improves search performance, and prevents indexing bottlenecks.

To check the total number of issues on your board, go to Issues, then select Search for issues and apply your board’s filter.

Read our community blog about the boards limit

Jira Mobile plugin removal

ステータス: 実装済み (EAP 01)

In Jira 9.11, we deprecated support for the Jira mobile web interface. Now, in Jira 11.2, we’re removing the Jira Mobile plugin in favor of the Jira Data Center mobile app for iOS and Android.

Jira Service Management の機能

New REST API scopes for service accounts

ステータス: 実装済み (EAP 01)

We’ve added support for service accounts in Jira Service Management and Assets by introducing READ and WRITE scopes to public REST API endpoints. This update lets you control access for service accounts, so you can specify whether an integration or automation can read or write data through the API:

• Use READ for retrieving data.
• Use WRITE for making changes.

In this release, we’ve added the ScopesAllowed annotation. This change is part of our ongoing service accounts project for Data Center. Join the Early Access Program for service accounts

Link your Jira with Confluence through OAuth 2.0

ステータス: 実装済み (EAP 01)

You can now connect your Jira Service Management to the Confluence knowledge base, Assets Confluence attributes, and Assets-Confluence macro through OAuth 2.0. With OAuth 2.0, impersonation is automatic, and Jira will act as the logged-in user when making requests to Confluence.

To configure the integration, select the JSM_KB scope and set the Confluence incoming link to READ. The integration is compatible starting from the following versions:

• Jira Service Management Data Center 11.0
• Confluence Data Center 10.0
• Assets-Confluence macro 3.0.0