Preparing for Jira 10.5
This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira Software Data Center 10.5 and Jira Service Management Data Center 10.5.
Latest version
Here you can find information about the latest EAPs.
Application | Date | Number | Version (Maven) | Downloads |
|---|---|---|---|---|
Jira Software |
| 10.5.0-EAP02 | 10.5.0-m0003 | |
Jira Service Management |
| 10.5.0-EAP02 | 10.5.0-m0003 |
Summary of changes
This section provides an overview of the changes we intend to make so that you can start thinking about their impact on your apps. Once the updates are ready, we'll indicate when they’ve been implemented and in which milestone.
- Jira Software and Jira Service Management common features
- Jira Software features
- Jira Service Management features
Jira Software and Jira Service Management common features
End of Velocity method allowlist debug mode
Status: IMPLEMENTED (EAP 01)
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
Secure app installations with app signing
Status: IMPLEMENTED (EAP 02)
As we communicated in October 2024, in 2025 we’re rolling out app signing. This feature will enable better security and increase customer trust in what they install on their local instances.
If you upload your apps to Atlassian Marketplace, we’ve got you covered. Once Marketplace validates and approves your app, Atlassian will sign and trust all your apps by default; no additional action is needed. App signing affects only new app installations, previously installed apps won’t undergo verification.
Check out our community announcement for details on private builds
New Aggregation API is now available
Status: IMPLEMENTED (EAP 02)
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. Read the Aggregation API upgrade guide
The Aggregation API is part of the new abstraction layer included in the Search API released in Jira 10.4.
Deprecation of Lucene-specific modules
Status: IMPLEMENTED (EAP 02)
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
Jira Software features
Remove deleted users marked as inactive
Status: IMPLEMENTED (EAP 01)
You can now manually remove externally deleted users marked as inactive directly from the user management view. Learn how to remove a user
This feature is on by default. To turn it off, disable the com.atlassian.jira.user.allowDeleteExternallyDeletedUsers feature flag.
Email notification character change limit
Status: IMPLEMENTED (EAP 02)
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.
Jira Service Management features
Limit access to Assets data in Assets Confluence Macro
Status: IMPLEMENTED (EAP 01)
We're introducing the Object Schema Viewer Role support to the Assets Confluence Macro App. This role allows read-only access to assets in the Confluence macro.
This feature is compatible with Jira Service Management 10.5 or later and is backwards compatible with the Assets Confluence Macro app. However, for the best experience, we recommend using Assets Confluence Macro 2.1.0 or later.
Group queues to organize issues
Status: IMPLEMENTED (EAP 01)
To help agents stay focused on the issues that are critical to their teams, we’re adding the possibility of organising queues (filtered sets of issues). Project admins can now group those queues to enhance agents' prioritization and streamline their workflows.