Last updated Dec 7, 2023

Rate this page:


If you're a Jira Data Center app developer, use this page to track upcoming changes, deprecation notices, new features, and feature updates on the Jira Data Center platform.

7 December 2023

Announcement Introducing SBOM for Jira Software, Jira Core, Jira Service Management Server and Data Center

We're happy to introduce the Software Bill of Materials (SBOM) in Jira Software, Jira Core, and Jira Service Management Server and Data Center. SBOM is a list of all the components present in a codebase. This can include open-source software, commercial software, hardware drivers, libraries, modules, and other elements.

More details

How to find SBOM

You can find SBOM in every Jira Software, Jira Core, and Jira Service Management Server and Data Center distribution (.zip, .tar.gz, .bin, .exe) starting from the following releases:

  • Jira Software 8.20.29, 9.4.14, 9.12.1

  • Jira Core 8.20.29, 9.4.14, 9.12.1

  • Jira Service Management 4.20.29, 5.4.14, 5.12.1

To locate the SBOM, go to sbom/ folder for any distribution and search for a file named according to the following pattern:<product_name>-<version>-cyclonedx-sbom.json.


  • Jira Core - atlassian-jira-9.4.14-cyclonedx-sbom.json

  • Jira Software - atlassian-jira-software-9.4.14-cyclonedx-sbom.json

  • JSM - atlassian-jira-servicedesk-5.4.14-cyclonedx-sbom.json

The current SBOM contains backend dependencies. We're working hard to add frontend dependencies as well.

30 November 2023

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Update issue descriptions in bulk edit mode

To make the issue editing process faster and more efficient, we’ve added a new bulk edit operation — Change description. Learn more about bulk changes in Jira

More details

The new feature lets users auto-modify the descriptions of any selected issues in several ways:

  1. Options for updating the description field:

    1. Replace existing: replace the current description with new text

    2. Add before existing: add text at the beginning of the current description

    3. Add after existing: add text at the end of the current description

  2. A text field for the issue description

To bulk edit issue descriptions, you need to have the Edit issues permission for all selected issues. Learn more about permissions in Jira

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Comment sorting is now saved in user preferences

Comment sorting is now saved for each user individually, and won't reset to the default "newest first" option when the user session ends.

This means that once a user selects to view the newest or oldest displayed comments first, Jira will always remember this choice. The comments will be displayed in the same way unless the user changes the sort order.

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Add watchers while creating issues

Users can save time while keeping the team updated by adding watchers as they create issues. No need to waste time creating an issue and then immediately editing it to add watchers! When the issue is created, Jira automatically adds the selected person as a watcher. If the added person isn’t in the correct project for the issue, Jira will show an error message and won’t add them as a watcher.

More details

To use this feature, the admin must enable the feature flag com.atlassian.jira.initialwatchers.enabled. Learn how to enable dark features in Jira

If Jira users already have a third-party app that offers similar functionality, the admin needs to disable the app before enabling the feature flag. Otherwise, the watchers will receive double notifications: one from the app and one from Jira.

To add watchers:

  1. In the Create issue dialog, go to Watchers.

  2. Start typing to find the people you’d like to watch this issue.

  3. Select a person to add them as a watcher.

Watchers field in the Create Issue dialog

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Secure a database password in HashiCorp Vault

Users can secure their passwords by storing them in HashiCorp Vault. Admins can now enable the SecretStore implementation to read a database password from a Vault instance. This is an alternative, more secure option for storing database passwords as plaintext in an XML file.

More details

The instructions below assume that a Hashicorp Vault instance is already running for the Jira instance. If it’s not, check out the Hashicorp Vault documentation.

To configure Jira to work with HashiCorp Vault:

  1. Create a secret in your HashiCorp Vault instance.

  2. Create a policy with permission to read your secret.

  3. Authenticate Jira with Vault.

  4. Add the Vault configuration data to the <home-directory>/dbconfig.xml config file.

Learn more about securing a database password in HashiCorp Vault

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Run multiple Assets imports in parallel

You can now run as many parallel imports as your system can handle, whether it’s on one node or multiple nodes. By default, Jira Service Management lets you run up to five parallel imports across your cluster. You can adjust the number of parallel imports based on the capacity of your cluster.

More details

To configure this setting:

  1. Log in as a Jira admin.

  2. Navigate to Administration > Manage apps > Assets configuration.

  3. In the General configuration section, edit the number set in Maximum parallel imports.
    If you don’t want to use parallel imports, set this to 1.

You don’t need to restart Jira after changing this setting, and this change won’t affect the imports that are already in progress.

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Edit request details inline from the queue view

Agents can now transition the request status and modify other details — like assignee and priority — directly from queues, instead of navigating to the issue view to edit fields.

We also removed the information icons next to the Assignee, Reporter, and Creator fields in the queue view and replaced them with avatars.

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Store Assets attachments in the S3 object storage

In Jira Software Data Center 9.11, we introduced the ability to store Jira attachments in Amazon S3 object storage. Now, you can store Assets attachments in the same Amazon S3 bucket.

More details

If you’ve stored Jira attachments in S3 and are upgrading to Jira Service Management 5.13 or later, you’ll need to migrate your assets attachments to the same S3 bucket where your Jira attachments are stored.

Migrate all files in the <sharedhome>/data/attachments/insight/ directory to the attachments/insight/ folder in the S3 bucket where you store Jira attachments. Learn how to migrate your attachment data to Amazon S3

Note that groovy scripts used in Assets automation rules will always be loaded from the filesystem and never from an S3 bucket.

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Get information about the user’s last login time via REST API

We’ve added the lastLogin field to the /rest/api/2/user?username REST API’s response that retrieves the user’s last login time. By using the information from this field, Jira system admins can quickly detect inactive users and deactivate their accounts, enhancing the security of your application.

More details

The API response with the lastLogin field looks like this:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 { "self": "", "name": "fred", "emailAddress": "", "avatarUrls": { "24x24": "", "16x16": "", "32x32": "", "48x48": "" }, "displayName": "Fred F. User", "active": true, "timeZone": "Australia/Sydney", "lastLogin": "2011-07-05T11:05:00.000+0000" "groups": { "size": 3, "items": [ { "name": "jira-user", "self": "" }, { "name": "jira-admin", "self": "" }, { "name": "important", "self": "" } ] }, "expand": "groups" }

Check out this ticket for more details about the update:

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Atlassian User Interface (AUI) upgrade

We've bumped the Atlassian User Interface (AUI) library from 9.3.18 to the newest 9.9.1 version.

To learn more about the updates, check out:

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Polyfills are completely removed from Jira

In Jira 9.2, we’ve removed a bunch of polyfills from the Jira Software code because they were no longer used on the currently supported browsers. In this release, we’ve removed the last polyfill — escape-css-selector-polyfill.

You can now use the widely supported CSS.escape static method as an alternative. If you want to read more about the previous updates, check out Preparing for Jira 9.2.

Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Upgraded dependencies and libraries

We’re constantly putting more focus on upgrading core components and libraries in Jira to improve security. Here’s a list of libraries that we’ve already upgraded.

More details



Source varsion

Target version

Important notes


Servicemix bundles are replaced by the com.atlassian.platform.dependencies:platform-spring-bundle



Servicemix is a set of repackaged versions of common libraries, prepared to be deployed in the OSGi environment. These packages are used in all DC products. The Servicemix release cycle is detached from the release cycles of the original libraries, which can cause delays in updates, especially in the case of security fixes. We’ve decided to create an alternative to Servicemix containing selected packages (com.atlassian.platform.dependencies:platform-spring-bundle). This approach allows for a faster adoption of updates and it doesn’t change anything for the plugin vendors and customers.


Atlassian Plugins





Atlassian Shared Access Layer (SAL)





Atlassian REST





Atlassian NavLinks





Atlassian Gadgets





Atlassian Webhooks





Atlassian OAuth 2





Atlassian Mail










Atlassian Seraph





Atlassian JSON





Atlassian Profiling





Atlassian AppLinks





Universal Plugin Manager





Atlassian User Interface (AUI)




We introduced the Design Tokens theme into AUI, making it possible to style the AUI components with the Design Tokens colors, which aligns the colors of the DC products with the Cloud ones and allows introducing the Dark mode.


Checker Framework





Commons IO





Commons Codec





Byte Buddy










Micrometer Core





Metrics JMX



















Announcement Jira Software 9.13 EAP 01 & Jira Service Management 5.13 EAP 01

Quickly access your favorite queues

Project admins and agents can now star frequently used queues for a quick and easy access.

The queues you star are:

  • displayed in a separate section at the top of all queues for quick access

  • also available within the queues list

  • associated with your personal account (they only appear in your view and won’t impact the view of other agents or admins)

More details

With this change, we’ve also modernized the experience of the queues sidebar. Use the expand and collapse icons to show and hide the list of queues.

To star a queue, navigate to your service project, select Queues, and then select the star icon next to your favorite queue.

26 October 2023

Announcement Jira Software 9.12 EAP 01 & Jira Service Management 5.12 LTS EAP 01

Jira 9.12 LTS EAP 01 and Jira Service Management 5.12 LTS EAP 01 are now available

The first early access program (EAP) releases of Jira 9.12 LTS and Jira Service Management 5.12 LTS are now available for testing. To find out more about breaking changes, new features, and introduced fixes, check out Preparing for Jira 9.12.

You can download the EAPs from this page. If you’re using, the versions are 9.12.0-m0001 and 5.12.0-m0001.

If you want to share your feedback or discuss the latest EAP releases, just leave a reply in the Atlassian Developer Community thread.