This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 9.12 and Jira Service Management 5.12.

Jira Software 9.12.x and Jira Service Management 5.12 are the last releases to support Server licenses

Jira Software 9.12 and Jira Service Management 5.12 will be the last releases available to download for Server, prior to the Server end of support on Feb 15, 2024. All following releases will only support our Data Center offering. As Jira Software 9.12 and Jira Service Management 5.12 are long-term support (LTS) releases, they will continue to receive security and bug fixes until the end-of-support date on Feb 15, 2024.

We recommend that you migrate to the Atlassian Cloud offering or upgrade to Data Center to remain secure and supported.

変更の概要

Jira 9.12 is a long-term support (LTS) release. This LTS release contains all features introduced since the last LTS release (Jira 9.4.0) and provides fixes for known issues. You can use the EAP release to test your apps and make sure they run smoothly.

この要約は、深刻度および種類によって変更点をセクション分割しています。

• 重大な変更
• このリリースで導入された修正
• New features and non-breaking changes
• サポート対象プラットフォームの変更
• Updates to the Jira platform REST API
• 既知の問題

重大な変更

停止や中断を避けるために、アプリや統合で何を変更する必要があるか確認してください。このセクションの内容は、新しいものから古いものへと時系列に整理されています。

Jira 9.11: The allowlist for outbound HTTP requests in Jira Automation is now enabled by default

Jira Software Jira Service Management

Jira Automation 9.0 (Jira 9.11 にバンドル) のリリース以降、グローバル設定の [すべての URL を Jira 許可リストと照合します。] はデフォルトで有効になっています。つまり、要求している URL が許可リストにない場合、ルールを公開できなません。設定された URL が許可リストにない場合、この設定は既存のルールも壊します。ルールの実行に失敗すると、監査ログにエラーが表示されます。壊れたルールは、URL を許可リストに追加するか、許可リストの検証を無効にすることで修正できます。

この変更の詳細については、次のリソースをご覧ください。

• 自動化ルールを実行できないか、エラーにより有効化または編集できない
• Jira 9.11 への準備

Jira 9.11: The introduction of secret key masking changes the behavior of the Webhook URL field in Jira Automation 

Jira Software Jira Service Management

In Jira Automation 9.0 (bundled with Jira 9.11), the Webhook URL field that appears when you create a rule with the Send web request action is now a menu instead of a text field. For a webhook URL to become available in the menu, you’ll need to add it as a secret key.

この変更の詳細については、次のリソースをご覧ください。

• 自動化ルール向けのマスクされたシークレット キーの作成と編集
• Jira 9.11 への準備

Jira 9.11: Amazon S3 オブジェクト ストレージのサポートを有効にすると、一部の API クラスが壊れる可能性がある

JIRA SOFTWARE JIRA SERVICE MANAGEMENT DATA CENTER

一部の Jira API は、Amazon S3 オブジェクト ストレージ方式と互換性がありません。つまり、これらの API をまだ使用しているアプリは、正しく機能しない可能性があります。対象の API は次のとおりです。

• com.atlassian.jira.config.util.AttachmentPathManager
• com.atlassian.jira.util.AttachmentUtils

For more details, check out Preparing for Jira 9.11.

Jira 9.8: Removal of the Xalan library

JIRA SOFTWARE DATA CENTER

We’ve removed the xalan library from the Jira Core codebase. As the library is no longer exported in OSGi, we've also removed the OSGi import from version 8.1.51 of jira-testkit-plugin. To make sure that your builds and tests won't fail, you might need to update jira-testkit-plugin to the newer version.

For more details, check out Preparing for Jira 9.8.

Jira 9.7: Performance improvements on jira-agile pages

JIRA SOFTWARE DATA CENTER

As a result of the performance-related updates to jira-agile pages, the following breaking changes have been introduced:

We are now exposing only a small subset of previously available AMD modules.

• We’ve left global variables intact. However, they’re also non-API parts and we don’t recommend using them in your apps.
• If your app uses an Agile module, it’s important to make the dependency explicit and not rely on transitive dependencies.

For more details, check out Preparing for Jira 9.7.

Jira 9.7: The updated Backbone library introduces breaking changes to the WebResourceManager

Jira Software Jira Service Management

Starting with Jira 9.7, <jira.webresources:ajs-backbone-amd-shim> from <web-resource key="util"> is no longer available.

Additionally, to ensure that your apps work correctly with Backbone 1.3.3, update your dependency on Backbone to jira.webresources:backbone-1.3.3 instead.

For more details, check out Preparing for Jira 9.7.

Jira 9.5: Jira が Log4j 2.x に移行

Jira Software Jira Service Management

Log4j をバージョン 2.17.2 にアップグレードしましたこれは大幅な変更であるため、既存のカスタムの Log4j 1.x 環境とこの Jira リリースとの互換性を確認するために追加の作業が必要になる可能性があります。

For more details, check out Preparing for Jira 9.5.

このリリースで導入された修正

Jira 9.12 and Jira Service Management 5.12 also introduce their own set of changes that fix known issues, boost performance, or improve the overall user experience.

Secure webhook communication between Jira and linked DVCS accounts

JIRA SOFTWARE

Jira が信頼できるソース コード リポジトリからのみ Webhook リクエストを受け付けるように、シークレット トークンのサポートを追加しました。今後、Jira はリンクされているすべての DVCS アカウントに対して自動的に Webhook シークレット トークンを生成し、設定します。

詳細は、「Webhook セキュリティの設定」を参照してください。

Support for custom SecurityTypes for assignees, watchers, reporters, and mentions

Jira Software Jira Service Management

We've fixed the bug that prevented users from seeing customers in the reporter user picker that should have access to the issue from Service project customer — portal access permission.

Additionally, the assignee, reporter, watcher, and mention user pickers in comments and issue descriptions now correctly show users with custom permission types. This fixes the issue in the case of:

• JSM's Service project customer — portal access permission in the reporter field,
• Jira's optional Reporter (show only projects with create permission) or Assignee (show only projects with assignable permission) permissions.

Spring library upgrade

Jira Software Jira Service Management

In Jira 9.12.18 and Jira Service Management 5.12.18, we've upgraded the Spring library to a version that no longer includes the org.springframework.remoting packages. This change doesn't affect the functionality of Atlassian Marketplace apps.

However, if you're using custom-built apps, we recommend verifying their compatibility to ensure that these applications work as expected.

新機能、修正、および重大な変更以外の変更

Get a glimpse of all the new features, fixes, and non-breaking changes added to each release leading up to Jira 9.12. The list is divided into sections by release. Every section contains a link to the corresponding release's EAP documentation, where you can learn the details.

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

このセクションには、前回の Jira LTS リリース以降にサポート対象プラットフォームに加えられたすべての変更の概要が含まれています。

新たにサポート対象となったプラットフォーム

Jira は次のプラットフォームをサポートします。

• PostgreSQL 15 (Jira 9.10)
• Microsoft SQL Server 2022 (Jira 9.10)
• PGpool-II (Jira 9.10)
• H2 組み込みデータベースのバージョン 2 (Jira 9.5)
• Java 17 (Jira 9.5)

サポート終了

次のプラットフォームのサポートは完全に削除されました。

• The Android 4.0 モバイル ブラウザ (Jira 9.5)
• Microsoft SQL Server 2016 (Jira 9.7)

Support for the platforms on this list will be removed in this release:

• PostgreSQL 10 and 11 (deprecated in Jira 9.9)
• Oracle 12c R2 (deprecated in Jira 9.9)

サポート廃止

Support for the following platforms remains deprecated in this release:

• Java 8 (deprecated in Jira 9.7)

Updates to the Jira platform REST API

If you're interested in what's changed between different versions of the Jira platform REST API, take a quick look at the Jira 9.12 REST API change log.

既知の問題

This section contains information about any issues that we’ve discovered in our testing. We’re constantly keeping an eye out, and if we find anything, we’ll post it here.

SchedulerService throws a ClassNotFoundException error

Jira Software Jira Service Management

In Jira 9.12.0 all plugins that implement SchedulerService and pass a serializable as a parameter are affected by a ClassNotFoundException error that occurs when LazyJobDetails loads the parameter map. If your plugin doesn’t implement SchedulerService, your instance is not affected. There is no known workaround for this issue.

We've delivered a fix in Jira 9.12.1.

For more information, go to the following Jira issue:

JSWSERVER-25377 - 課題情報を取得中... ステータス

The Install4J library throws an exception when running the Jira installer for Linux on Java 17

Jira Software Jira Service Management

Java 17 has been supported since Jira 9.5.0. In Jira 9.11.0, we've started to bundle Java 17 with Jira binaries (both archives and installers) for Linux and Windows. There is a known issue with the Install4J runtime library, in which the Linux installer running on Java 17 throws a method invocation exception.

For more details, check out Install4J runtime library throws exception when running the Jira 9.11 installer on Linux.