Jira Service Management 10.2.x release notes

20 November 2024

We're excited to present Jira Service Management 10.2.

Highlights

• Restrict comment visibility to a group or role
• Automatic approver refresh for Assets custom fields
• Preventing data loss when changing cardinality in Assets
• Accessibility improvements for low-vision and keyboard-only users
• New login experience with two-step verification
• Turn off the lights in Jira automation
• Your logo in light and dark
• New header color in the original theme
• Image attachments thumbnails in emails
• Secrets management just got more secure
• Jira automation support for Microsoft Teams webhooks
• Component validations for disabled automation rules
• Connectivity check for sharing usage data
• Integrity Checker improvements
• Changes to metrics served by the JMX exporter
• Alert, metric, and statistics logs in Jira automation
• Resolved issues

Get the latest version

More

Read the Jira Service Management 10.2 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.2.x release notes
• Jira Software 10.2.x upgrade notes

Restrict comment visibility to a group or role

For: AGENTS ADMINS

We’re improving the way agents and admins share information when commenting on issues. In service projects, they can now restrict comments not only to all internal users but also to specific roles or groups they belong to.

Automatic approver refresh for Assets custom fields

For: AGENTS ADMINS

We've improved how approvers are managed in workflows using Assets custom fields. Now, if you update the value of an Assets custom field or modify the attributes of associated Asset objects, the list of approvers will refresh immediately. This ensures that the right people are always in the loop. New approvers will also receive notifications about their pending tasks.

Preventing data loss when changing cardinality in Assets

For: ADMINS

We've improved how attribute cardinality changes are managed in Assets. So far, if an attribute's values exceeded the maximum cardinality, excess values were silently deleted during re-indexing. This could result in a data loss. Now, when you reduce the maximum cardinality of an attribute, a new dialog box will appear, allowing you to choose whether to keep or delete the excess values. If you delete them, this action will be recorded in the object's history. This change gives you more control over your data.

Accessibility improvements for low-vision and keyboard-only users

For: END USERS

As promised, we’re bringing more accessibility updates for screen reader and keyboard-only users removing the critical severity defects. The highlights for this release include corrections for the underlying HTML structure or JS logic.

Check out the full list of fixed issues

New login experience with two-step verification

For: END USERS ADMINS

We’ve overhauled the Jira login experience and added a second authentication layer to keep your account secure. You can now set up two-step verification and verify your identity with an authentication app when you log in to protect your Atlassian account. Explore how to manage two-step verification

Turn off the lights in Jira automation

For: END USERS ADMINS

In Jira 10.0, we announced that the dark theme became partially available for the first time and listed the areas that weren’t supported at that moment. Now, in Jira 10.2, we’re bringing dark theme to Jira automation. To test your rule components' compatibility, enable the dark theme by going to your Profile, then Theme, and select Dark.

Your logo in light and dark

For: ADMINS

You can now upload your site logo in two versions so it matches your theme whether you choose the light or dark option. If you upload just one logo, it'll apply to both themes. If you’re already using your own logo, it'll now become the light theme logo.

To upload your logo, go to Administration, then System, then Look and feel, then Logo.

New header color in the original theme

For: ADMINS

As part of our ongoing implementation of the new light and dark themes, we’ve changed the color of the original theme’s header from blue to white.

Image attachments thumbnails in emails

For: END USERS ADMINS

You can now see thumbnails of image attachments in emails without being authenticated to Jira. This update fixes the problem of images not being rendered properly while having issues with authentication.

This feature is on by default. To disable it, turn off the following feature flag: com.atlassian.jira.send.email.notifications.with.images.attached.

Secrets management just got more secure

For: ADMINS

As part of our ongoing efforts to make Jira more secure, we’re now by default encrypting the most sensitive values that Jira needs for operation. Secrets previously stored in Jira with AES or using external vaults (AWS Secrets Manager or Hashicorp Vault) are now located in the secret database table in an encrypted form.

All the places that previously contained secrets (e.g. database columns with passwords) now contain an {ATL_SECURED} placeholder instead of the plaintext secret. The only exception is the database password. Check out the upgrade notes for more details on the database password

Encryption keys are stored in the keys subdirectory of your Jira home directory (for single node instances) or shared home directory (for clustered instances). These need to be backed up, along with secrets-config.yaml and secured, as a database backup restored without encryption keys won’t be able to use encrypted secrets.

Jira automation support for Microsoft Teams webhooks

For: ADMINS

Recently, Microsoft announced the retirement of Office 365 connectors within Microsoft Teams. To ensure seamless communication between the automation rules and Microsoft Teams, we developed a workaround that allows you to create your own connectors. Now, you can create a flow chain that will listen to Jira webhooks. This feature is available starting from the following Jira versions.

More about using Jira automation with Microsoft Teams

Component validations for disabled automation rules

For: ADMINS

Component validations are now performed both for enabled and disabled automation rules when they’re updated. This ensures that all rules undergo validation to quickly identify any configuration errors.

Connectivity check for sharing usage data

For: ADMINS

When you share your instance usage data, your firewall setup ensures data can be sent outwards. You can now test the connection to check if your firewall prevents or causes traffic blockages. More about sharing usage data

Integrity Checker improvements

For: ADMINS

We’ve improved the Integrity Checker so that it works at the Enterprise scale. Now, it won’t cause high JVM memory pressure or full garbage collection anymore. Finding issues is much faster, and fixing them is more extensive and precise.

For the long-running fix operations, we’ve implemented a limit of fixes within a single check jira.integrity.checker.results.limit that defaults to 1000 and can be adjusted. We’ve also limited the default number of displayed results to 20.

Changes to metrics served by the JMX exporter

For: ADMINS

We no longer expose Connection instance-level metrics through the JMX exporter in Jira while still maintaining other types of tracking, including tracking at the Connections level.

Up until now, we exposed Connection-level metrics together with Connection instance-level metrics.

We no longer expose Connection instance-level metrics while still maintaining all the information from Connection-level metrics.

If you need to restore the previous behavior, you can use the parameter -Ddbcp.registerConnectionMBean=true to override those settings. However, this workaround isn’t recommended as it may bring back already fixed symptoms or cause other unknown problems resulting from the thread races in the underlying library.

Alert, metric, and statistics logs in Jira automation

For: ADMINS

To enhance the monitoring capabilities of the automation queues, we’re introducing alert, metric, and statistics logs. Every five minutes, a log will report on the number of messages added, claimed, and processed from the queue, as well as the number of rules executed. If the automation queue exceeds a configurable threshold of 10,000, the Jira diagnostics screen will display an alert. The queue length is now also available as a JMX metric.

Resolved issues

See the full list of the issues we’ve resolved throughout the lifecycle of Jira Service Management 10.2.