Jira Software 10.5.x リリース ノート
Jira Software 10.5 がリリースされました!
ハイライト
さらに読む
本リリースに関する重要な情報をアップグレード ノートで確認し、解決済みの課題の完全な一覧をご確認ください。
互換性のあるアプリケーション
互換性のある Jira アプリケーションをお探しの場合、次のページをご参照ください。Jira Service Management 10.5 リリース ノート
Secure app installations with app signing
対象: 管理者
To improve app security, we’re introducing a new feature that will restrict app installations to only those that are signed. This will help us to:
- ensure that apps are either from Atlassian Marketplace or manually uploaded by trusted partners
- prevent malicious actors from uploading harmful apps
App signing affects only new app installations, already installed apps will remain intact.
This feature will be gradually rolled out across Data Center products by mid-2025. For details, check out this community post.
In this release, app signing is disabled by default. The grace period will last until the next feature release of Universal Plugin Manager (UPM), after which app signing will be enabled by default.
Use the grace period to adapt your processes. The steps you need to take differ depending on whether you install applications from the Marketplace or build your custom applications.
Enable app signing and install from Marketplace
During the grace period, you can enable app signing at your convenience. To do so:
- Enable app signing. For details, see Configuring UPM app signature check.
- Download and install Certificate Authority (CA) from Atlassian. For details, see Updating Atlassian Certificate Bundles.
- That’s it! Enjoy the safe app installations from Marketplace.
カスタム アプリのインストール
If you use custom application builds, you can sign and secure your apps:
- Enable app signing. For details, see Configuring UPM app signature check.
- Get the app signature and verification certificate as described in Generating app signature and verification certificate using OpenSSL.
- Put your new certificate in your Trust store as described in Updating Atlassian Certificate Bundles.
- Install the signed application.
You can also install the app via the file system without using the app signing feature.
If you’re experiencing issues, check out app signing troubleshooting.
データ パイプライン エクスポートをより細かく制御して時間と容量を節約する
対象: 管理者
You can now use an opt-out list to exclude CSV files from data pipeline exports. This may save disk space and time, especially if your Jira instance includes large CSV files that you don’t need to export. This opt-out feature was introduced in Data Pipeline version 3.2.0.
For more context, see the Data pipeline page.
For full details, including how to remove files from the opt-out list and get the list of files supported, see the Data pipeline REST API reference.
New Aggregate API now available
対象: 管理者
The new Aggregation API is now available, replacing the deprecated Lucene Collectors. This API introduces two aggregation types: metric and bucket aggregations, enhancing the flexibility and functionality of your search capabilities. To use this new API, enable it through a feature flag: com.atlassian.jira.aggregation.api.
The Aggregation API is part of the new abstraction layer included in the Search API released in Jira 10.4. Read the Aggregation API upgrade guide
Deprecation of Lucene-specific modules
対象: 管理者
In Jira 10.4, we added a new abstraction layer to Jira’s search functionality and introduced a new search API. Now, in Jira 10.5, two more Lucene-specific modules have been deprecated in favor of the platform-agnostic search API. Read the Search API upgrade guide
End of Velocity method allowlist debug mode
対象: 管理者
As we previously announced, we’re disabling the debug mode by default for the Velocity method allowlist. Every Velocity method which isn’t added to an allowlist will be blocked.
If your apps aren’t compatible with this change or you’re experiencing any issues, you can enforce the debug mode again by setting up the system property atlassian.velocity.method.allowlist.debug to true, e.g. -Datlassian.velocity.method.allowlist.debug=true. Learn how to configure the Velocity method allowlist
非アクティブとしてマークされた削除済みユーザーの削除
対象: 管理者
非アクティブとしてマークされ、外部から削除されたユーザーを、ユーザー管理ビューから手動で直接削除できるようになりました。ユーザーの削除方法をご確認ください。
この機能は既定でオンになっています。オフにするには、com.atlassian.jira.user.allowDeleteExternallyDeletedUsers 機能フラグを無効にします。
Email notification character change limit
対象: 管理者
The processing of the outgoing mail queue is single-threaded and can get delayed or stuck in case of notifications where it takes a long time to calculate changes in an issue. This is why we’ve added a limit to the maximum number of characters we’ll calculate the difference between the original and the new content for. If that limit is exceeded, the email notification will contain a message saying there are too many changes to display instead of showing the exact difference.
You can configure the character limit value via the jira.email.diff.max.characters system property.
解決済みの課題
See the full list of the issues we’ve resolved throughout the lifecycle of Jira Software 10.5.