Jira Service Management 10.5.x release notes
12 March 2025
We're excited to present Jira Service Management 10.5.
Highlights
- Group queues to organize issues
- Limit access to Assets data in Assets Confluence Macro
- Secure app installations with app signing
- Save time and space with more control over data pipeline exports
- New Aggregate API now available
- Deprecation of Lucene-specific modules
- End of Velocity method allowlist debug mode
- Resolved issues
e
More
Read the Jira Service Management 10.5 upgrade notes for important details about this release and see the full list of issues resolved.
Compatible applications
If you're looking for compatible Jira applications, look no further:
Group queues to organize issues
For: PROJECT ADMINS AGENTS
To help agents stay focused on the issues that are critical to their teams, project admins can now group and arrange queues, which are filtered set of issues. This enhancement streamlines agents' workflows and improves prioritization.
To group queues, navigate to your service project and then, from the sidebar, select Queues. The Queue settings appears below the list of all the queues. The new groups of queues will appear at the top of the queue list. Explore how to set up queues for your team
1: Queues
2: Queue settings
Limit access to Assets data in Assets Confluence Macro
For: ADMINS
We're introducing the Assets Viewers role to the Assets Confluence Macro App. This role allows read-only access to assets in the Confluence macro. To grant the new role, navigate to your schema configuration, and then go to the Roles tab. Explore how to configure Assets roles and permissions
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.
The following features live in the Jira Data Center platform, which means it's available for Jira Software and Jira Service Management.
Secure app installations with app signing
For: ADMINS
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.
Install custom apps
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.
Save time and space with more control over data pipeline exports
For: ADMINS
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
For: ADMINS
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
For: ADMINS
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
For: ADMINS
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
Resolved issues
See the full list of the issues we’ve resolved throughout the lifecycle of Jira Service Management 10.5.