Rate this page:
We've moved the communication about Jira Software Data Center and Jira Service Management Data Center releases and updates to this changelog. With this transition, we aim to provide partners and developers with a customizable feed of improvements and changes to our products.
You can continue using the Atlassian Developer community for discussion and support. Subscribe to the category to stay tuned!
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.
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.
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.
Example
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.
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
The new feature lets users auto-modify the descriptions of any selected issues in several ways:
Options for updating the description field:
Replace existing: replace the current description with new text
Add before existing: add text at the beginning of the current description
Add after existing: add text at the end of the current description
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
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.
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.
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:
In the Create issue dialog, go to Watchers.
Start typing to find the people you’d like to watch this issue.
Select a person to add them as a watcher.
Watchers field in the Create Issue dialog
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.
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:
Create a secret in your HashiCorp Vault instance.
Create a policy with permission to read your secret.
Authenticate Jira with Vault.
Add the Vault configuration data to the <home-directory>/dbconfig.xml config file.
Learn more about securing a database password in HashiCorp Vault
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.
To configure this setting:
Log in as a Jira admin.
Navigate to Administration > Manage apps > Assets configuration.
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.
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.
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.
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.
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.
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": "http://www.example.com/jira/rest/api/2/user?username=fred",
"name": "fred",
"emailAddress": "fred@example.com",
"avatarUrls": {
"24x24": "http://www.example.com/jira/secure/useravatar?size=small&ownerId=fred",
"16x16": "http://www.example.com/jira/secure/useravatar?size=xsmall&ownerId=fred",
"32x32": "http://www.example.com/jira/secure/useravatar?size=medium&ownerId=fred",
"48x48": "http://www.example.com/jira/secure/useravatar?size=large&ownerId=fred"
},
"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": "http://www.example.com/jira/rest/api/2/group?groupname=jira-user"
},
{
"name": "jira-admin",
"self": "http://www.example.com/jira/rest/api/2/group?groupname=jira-admin"
},
{
"name": "important",
"self": "http://www.example.com/jira/rest/api/2/group?groupname=important"
}
]
},
"expand": "groups"
}Check out this ticket for more details about the update: https://jira.atlassian.com/browse/JRASERVER-33225
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:
CHANGELOG: the scope of changes and related issues
AUI upgrade guides: guidelines for upgrading to each AUI version
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.
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.
Component | Source varsion | Target version | Important notes | |
|---|---|---|---|---|
| 1 | Servicemix bundles are replaced by the |
|
| 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 ( |
| 2 | Atlassian Plugins |
|
|
|
| 3 | Atlassian Shared Access Layer (SAL) |
|
|
|
| 4 | Atlassian REST |
|
|
|
| 5 | Atlassian NavLinks |
|
|
|
| 6 | Atlassian Gadgets |
|
|
|
| 7 | Atlassian Webhooks |
|
|
|
| 8 | Atlassian OAuth 2 |
|
|
|
| 9 | Atlassian Mail |
|
|
|
| 10 | WRM |
|
|
|
| 11 | Atlassian Seraph |
|
|
|
| 12 | Atlassian JSON |
|
|
|
| 13 | Atlassian Profiling |
|
|
|
| 14 | Atlassian AppLinks |
|
|
|
| 15 | Universal Plugin Manager |
|
|
|
| 16 | 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. |
| 17 | Checker Framework |
|
|
|
| 18 | Commons IO |
|
|
|
| 19 | Commons Codec |
|
|
|
| 20 | Byte Buddy |
|
|
|
| 21 | JSoup |
|
|
|
| 22 | Micrometer Core |
|
|
|
| 23 | Metrics JMX |
|
|
|
| 24 | ROME |
|
|
|
| 25 | Guava |
|
|
|
| 26 | BouncyCastle |
|
|
|
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)
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.
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 maven.atlassian.com, 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.