Automation queue supportability improvements

Jira Service Management 10.4.x release notes
22 January 2025

We're excited to present Jira Service Management 10.4.

Highlights

• Say goodbye to clutter and hello to better performance
• Automation queue supportability improvements
• Rotate your encryption keys like clockwork
• Customize the order of issue link types
• New Jira Stats logging location
• New Search API now available
• Resolved issues

More
Read the Jira Service Management 10.4 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:

• Jira Software 10.4.x release notes
• Jira Software 10.4.x upgrade notes

Say goodbye to clutter and hello to better performance
For: ADMINS

Over time, data piles up and complex permissions can slow things down. Simplify your workflow by using APIs to cut down on permission checks, making it easier to find what you need and boosting performance:

• GET https://{baseURL}/rest/servicedeskapi/organization/cleanup that retrieves organizations to be deleted.
• DELETE https://{baseURL}/rest/servicedeskapi/organization/cleanup that deletes specified organizations.
  You can also delete organizations with inactive users and delete detached organizations from these endpoints. Explore new REST API endpoints

Automation queue supportability improvements
For: ADMINS

Sometimes, when the automation queue grows, rule execution can be delayed or remains unexecuted. To enhance the monitoring capabilities of the automation queues, we’re introducing new alerts, metrics, and diagnostic REST endpoints:

• Alerts will now appear on the Diagnostics page when the unprocessed and unclaimed messages in the automation queue surpass the configurable threshold configurable threshold (defaults to one hour).
• You can see a new instrumentation and JMX metric (automation.queue.earliest.unprocessed.message.age.secs.max_stale_10mins) that reflects the age of the oldest unprocessed and unclaimed message in the queue.
• You can use new API endpoints to analyze events and rules that are contributing to the queue growth:
• GET /rest/cb-automation/latest/insight/automation-queue/by-event-type that retrieves and groups the contents of the automation queue by event type.
• GET /rest/cb-automation/latest/insight/automation-queue/by-rule that retrieves and groups the contents of the automation queue by rule.
• GET /rest/cb-automation/latest/insight/audit/by-event-source that analyzes audit logs and groups them by event source for a specified timeframe.

Rotate your encryption keys like clockwork
For: ADMINS

Jira already automatically encrypts plaintext secrets through default secrets encryption. Now, you can further protect your system through encryption key rotation. Use API calls to re-encrypt your existing secrets with a new key, and to manage your inactive keys. This extra security is available for both single-node and clustered environments. Details on encryption key rotation

Customize the order of issue link types
For: ADMINS

Admins can now customize the order of issue link types. We’ve introduced two sorting methods:

• Drag and drop: Rearrange the order directly in the issue link type table.
• Sort alphabetically: Use the dropdown menu to sort in ascending or descending order.

New Jira Stats logging location
For: ADMINS

Starting from Jira 10.4.0, Jira Stats will be logged to atlassian-jira-stats.log instead of atlassian-jira.log. This is configured by the log4j2.xml properties. Learn more about logging in

Tools like Splunk, Grafana, Logstash, Kibana, or any other that rely on Jira Stats must be adapted to the new file location. If the log4j2.xml configuration file is overridden, adapt it manually:

New Search API now available
For: ADMINS

We're laying the foundations for more agnostic option for search tooling, starting with adding an abstraction layer. This change is key to enable future OpenSearch support. The new abstraction layer introduces a new Search API. Search and indexing performance will remain consistent with the existing Lucene implementation. This change also marks the start of our plans to remove Lucene from public APIs. Read the Search API upgrade guide

Resolved issues
Issues resolved in 10.4.0

• JSDSERVER-15929 Projects | Waiting for support : Expand/collapse state of the button not defined
• Bug JSDSERVER-15848 SLA JQL search creates large Lucene query from high number of projects and goals
• Bug JSDSERVER-15778 Help center | Home: Missing label for slider control
• Bug JSDSERVER-15755 Help center | Home: Buttons not focusable with keyboard lacks button role
• Bug JSDSERVER-15725 Sorting comments on issue view with pinned comments hangs
• Bug JSDSERVER-15717 Assets CF with project Context causes NullPointerException in logs and may cause JQL issue search performance degradation [Regression of JSDSERVER-15428]
• Bug JSDSERVER-15707 PAT is broken in customer portal when installed via OBR
• Bug JSDSERVER-15693 Comments are not created for some Request types due to ReplyTo header being empty in customer notifications for request types that are not associated with any email channel
• Bug JSDSERVER-15634 Asset CF displays '&' as '&amp' while editing
• Bug JSDSERVER-15620 Sorting objects by reference attribute can cause inaccessible object view
• Bug JSDSERVER-15585 Assets Referenced Custom Fields do not show OutboundReferences
• Bug JSDSERVER-15583 Low rating CSAT is set unknowingly from the customer mail server client
• Bug JSDSERVER-15574 Main Customer Portal Search stop working when Confluence Cloud is linked with tunnel and cloud integration
• Bug JSDSERVER-15562 Assets referenced custom field is not displayed on some nodes in the customer portal
• Bug JSDSERVER-15363 Users without Assets Administrator role are unable to edit an email action within an object schema automation rule
• Bug JSDSERVER-15219 Attributes with the same name from different object types and schemas are searched against the database when the attribute is added to the Filter objects with attributes, resulting in long searching time
• Bug JSDSERVER-14217 Help center | approvals : Missing keyboard support for buttons
• Bug JSDSERVER-11906 Raise a Request : "Raise this request on behalf of" Combobox is missing appropriate roles and/or attributes.
• Bug JRASERVER-78388 UpgradeTask_Build960000 task fails due to hitting MSSQL maximum number of parameters limitation
• Bug JRASERVER-78346 Total Unique Issues for two dimensional chart from Jira Charts macro is redirecting user to invalid filter id error.