Jira Software 9.15.x release notes

Still need help?

The Atlassian Community is here for you.

Ask the community

More

Read the upgrade notes for important info about this release and see the full list of issues resolved.

 Compatible applications

If you're looking for compatible Jira applications, look no further:


Important changes to performance and scaling reports

We're making some changes to the way we create performance reports for Jira. To learn more and share your feedback, head over to Atlassian Community.

Introducing Software Bill of Materials (SBOMs) to Jira Software Data Center

Continuing our commitment to providing the most secure products for our customers, we’re introducing Software Bill of Materials (SBOMs) to Jira Software Data Center.

More information

What is SBOM and why are we adding them?

SBOM is a detailed list or inventory of all the components in a piece of software. These components can include open-source software, proprietary code, libraries, frameworks, and other elements used in the software.

SBOM is essential for ensuring compliance with different regulations and standards; for example, the Executive Order on Improving the Nation's Cybersecurity on Improving the Nation's Cybersecurity, the European Union NIS 2 Directive and Cyber Resilience Act. It enhances transparency and facilitates a deeper understanding of software components, their versions, dependencies, and updates to their security vulnerabilities.

Furthermore, SBOM can help app developers and admins identify potential security risks, manage licenses, and maintain software more effectively. For example, if a vulnerability is discovered in a specific open-source component, anyone with access to SBOM can quickly check if their software is affected.

How is SBOM generated

We use Syft, an open-source tool, to automatically generate SBOM files during the product build process. Syft scans the code, identifies dependencies, and compiles a JSON file with the results. Syft supports various SBOM formats, with CycloneDX being Atlassian's current choice due to its popularity.

Where to find SBOM

To locate the SBOM, go to the sbom/ folder in the installation directory of your Atlassian product and search for a file named with either of the following patterns: <product_name>-<version>-cyclonedx-sbom.json or <product_name>-<version>-sbom.cdx.json.

Check an example for Jira Software 9.15:

atlassian-jira-software-9.15-cyclonedx-sbom.json

Important to know

Due to the complex, plugin- and component-based architecture of our product suite, we are gradually revealing all front-end dependencies. Our current SBOMs cover a portion of these dependencies.

Restrict file extensions that can be uploaded to your Jira

Grab one more security feature out of the box! To protect your Jira instance and your organization’s infrastructure from potential malware, admins can now restrict unwanted file extensions from being uploaded through issues. To restrict specific file formats, you just need to create a blocklist or an allowlist of file extensions that must be blocked or allowed, respectively.

How to restrict file extensions

Tightening security with a websudo allowlist

To add an extra layer of security to websudo operations, you can configure and enable your own IP address/subnet allowlist for Jira. This means that certain superuser operations can only be performed from pre-approved IP addresses.

How to create a websudo allowlist

Confluence Page Viewer replaces the Confluence Page Gadget

In this release, we’re replacing the old and popular Confluence Page Gadget with the new Confluence Page Viewer. The new gadget is built on top of a modern and secure technology stack and comes with several UI improvements for a better overall experience. And just like with the old one, you can use the Confluence Page Viewer to embed a page from a linked Confluence Data Center site on your Jira dashboard.

About gadgets for Jira applications

Confluence Page Viewer dashboard gadget

Resolved issues

Scroll through the list of the issues we’ve resolved throughout the lifecycle of Jira Software 9.15.

Issues resolved in 9.15.0
Released on  

Due to a third-party app compatibility problem, this release has been removed and shouldn't be installed. We've delivered a fix for this problem in Jira Software 9.15.2, which is available for download.

Issues resolved in 9.15.1
Released on  

Due to a third-party app compatibility problem, this release has been removed and shouldn't be installed. We've delivered a fix for this problem in Jira Software 9.15.2, which is available for download.

Issues resolved in 9.15.2
Released on

With the Jira Software 9.15.2 release, the compatibility issues with third-party apps found in the previous 9.15.0 and 9.15.1 versions have been resolved by removing the REST v2 plugin. However, if you've already moved any plugins to REST v2, this removal might affect them. Plugins should rely on REST v2 starting from Jira Software 10.0 (EAP02) and later.

T Key Summary Status
Loading...
Refresh


Last modified on Nov 20, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.