Jira Software 11.0.x release notes

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: Jira Service Management 11.0 release notes.

Introducing the Jira Data Center connector for Rovo

For: END USERS ADMINS

The Jira Data Center connector facilitates Cloud-based AI capabilities without requiring a full migration to the Cloud and allows data synchronization from Jira Data Center to Rovo in Atlassian Cloud.

With Rovo, you can centralize knowledge from various platforms, providing a unified view of search results from both Cloud and Data Center, as well as third-party tools like SharePoint and Slack. You can boost productivity with Rovo Chat’s AI-driven insights and personalized responses, all while maintaining your existing infrastructure.

Coming soon: You’ll be able to also include Jira Service Management Data Center projects and issues in Rovo’s unified search and AI experiences.

Rovo, including search, chat, and studio apps as well as agents, is available to customers with a Premium or Enterprise Cloud plan of Jira, Confluence, Jira Service Management, or Teamwork Collection. Contact our team for assistance with setting up a new plan.

Already have access to Rovo? Connect Jira Data Center to Rovo

Removal of the deprecated Text gadget

For: END USERS ADMINS

We’ve removed the Text gadget for dashboards that we deprecated in Jira 9.11 and replaced with the Rich Text gadget to improve security in Jira.

End of support for the Original theme

For: END USERS ADMINS

With the new light and dark themes that brought accessibility and usability improvements, we’re removing the original theme from all products.

New look and feel for Advanced Roadmaps for Jira

For: END USERS ADMINS

In Jira 10.7, we introduced a new look and feel for Advanced Roadmaps for Jira. Now, in Jira 11, we’re removing the feature flag behind those changes, making the modernized UI the new standard. This change brings consistency in how you and your team view and manage projects.

New to Advanced Roadmaps? Discover Advanced Roadmaps for Jira

Changes to issue sources filter for unsaved issues in Advanced Roadmaps for Jira

For: END USERS

We’re updating how issue sources are attached to newly created issues in Advanced Roadmaps for Jira plans. Now, new issues won’t have any issue source attached until you save them to Jira. Previously, new issues were immediately linked to their issue sources, allowing filters to apply to both saved and unsaved issues.

Strict permission handling in Advanced Roadmaps for Jira

For: END USERS ADMINS

We’re adding strict permission handling for Jira issue filters used as an issue source in Advanced Roadmaps for Jira. Now, if you don’t have permission to view an issue filter, and that filter is used as an issue source in a plan, you won’t see the issues from that filter in your plan.

The new approach ensures that issue visibility in plans always respects Jira’s permission model, bringing consistency across Jira. To include new issues in your plans, make sure they’re saved in Jira and that you have access to the relevant filters.

Changes to System Dashboard operations

For: END USERS ADMINS

We’ve aligned the System Dashboard interface to accurately reflect permissible actions and prevent confusion:

• On the Shared Dashboards page, we've removed the dropdown menu with options to delete or change System Dashboard’s ownership.
• On the Manage Dashboards page, we’ve removed the Edit and Delete options. Now, you can only copy System Dashboard.

These changes apply exclusively to the System Dashboard. 

Sorting on TEXT entity property

For: END USERS ADMINS

We’ve removed support for sorting on TEXT entity properties. This also applies to existing TEXT entity properties.

Entity properties declared with more than one type

If the same entity property is declared more than one time, only the first declaration will be considered and the subsequent declarations will be ignored.

Considering the index-document-configuration module below, only the STRING property will be created.

<index-document-configuration entity-key="IssueProperty" key="IssueProperty">
    <key property-key="foo.bar">
        <extract path="foo1.bar2" type="string" alias="fb">
        </extract>
    </key>
    <key property-key="foo.bar">
        <extract path="foo1.bar2" type="date">
        </extract>
    </key>
</index-document-configuration>

You can confirm whether a property has been ignored by configuring a logging level of DEBUG for the com.atlassian.jira.search.issue.index.indexers.impl.IssuePropertyIndexExtractor package.

Upgrade from ProForma Lite to ProForma Full

For: ADMINS

The ProForma Lite app is no longer supported or available to download from the Atlassian Marketplace. Instead, you can now try a 30-day free trial of the full ProForma app to explore all ProForma features and enjoy a better forms experience.

If you currently use ProForma Lite, plan to upgrade to the full, paid version of the ProForma app or check out the trial first. ProForma Lite won’t receive updates, compatibility fixes, or support. It might also stop working if it becomes incompatible with future Jira updates.

If you’re using Jira Service Management, you can access all ProForma features for free. Explore ProForma licensing details

Advance notice: OpenSearch opt-in feature ready for early access

For: ADMINS

We’re working to introduce OpenSearch as an opt-in search engine in Jira. This will provide more advanced indexing options leading to less processing requirements and faster search results. We’re inviting you to be a part of our OpenSearch Early Access Program (EAP)! We’ve updated the OpenSearch upgrade guide to help you get started.

View your repo health with Sync history

For: ADMINS

We're introducing Sync history in the Distributed Version Control System (DVCS) admin section, a new feature that provides a repository sync audit log at a glance. Previously, admins couldn't access essential information about past repo syncs, making it challenging to assess the health of the sync process and debug errors.

Now, you can access a detailed list of repository syncs from the past seven days in the audit table, reducing the time you need to identify and isolate problem areas. The details include start and end time, sync status, failure reason, duration, and type of sync (soft or full).

To check the sync history of your repo:

1. Go to Settings, then Applications.
2. Go to DVCS accounts and open your account.
3. Next to the repo you want to check, select Show sync history.

New backend issue limit for Advanced Roadmaps for Jira

For: ADMINS

We’ve increased the backend limit of issues that Jira can return in Advanced Roadmaps to 10,000. This change helps keep performance stable and ensures safe operation when working with large volumes of issue data in your plans. The frontend limit is still 5,000 issues.

App signing is now enabled by default for app installations

For: ADMINS

In this release, app signing is enabled by default. This feature improves app security and was gradually rolled out across Data Center products. For details, check out this community post.

App signing affects only new app installations; already installed apps will remain intact.

The steps you need to take differ depending on whether you install applications from the Marketplace or build your custom applications.

Install apps from the Marketplace

To do so:

1. Configure the location of the truststore folder as described in Configuring UPM app signature check.
2. Download and install the Atlassian Certificates bundle. For details, see Updating Atlassian Certificate Bundles.
3. That’s it! Enjoy the safe app installations from the Marketplace.

Install custom apps

If you use custom application builds, you can sign and secure your apps:

1. Configure the location of the truststore folder as described in Configuring UPM app signature check.
2. Get the app signature and verification certificate as described in Generating app signature and verification certificate using OpenSSL.
3. Put your new certificate in your Trust store as described in Updating Atlassian Certificate Bundles.
4. Install the signed application.

You can also install the app via the file system without using the app signing feature.

If you’re experiencing issues, check out app signing troubleshooting.

Check indexing stats in JMX

For: ADMINS

We’ve added indexing statistics to the In-Product Diagnostics (IPD). Previously, you could see these statistics exported in jira-stats only. Now, you can also access them through Java Management Extensions (JMX). This change simplifies the integration of indexing statistics with your existing observability tools. More about live monitoring using the JMX interface

Faster user management

For: ADMINS

We've optimized the User Management view to reduce memory consumption and improve performance. Now, instead of navigating through all pages, the default display is limited to 10,000 users or 500 pages, which significantly reduces rendering time.

To adjust this limit, go to System, select Advanced settings, and change the value of the jira.user.management.browsable.results.limit property. More about managing users

Simplification of multipart handling in WebWork

For: ADMINS

We've removed several unused features of the WebWork library within Jira. These features weren't recommended for customization. If you've modified your webwork.properties file, ensure the following fields are set to their default values:

webwork.multipart.parser=custom
webwork.multipart.parser.class=com.atlassian.jira.web.TempFileRemovingMultipartRequestWrapper

Removal of Trusted apps

For: ADMINS

We’re removing Trusted apps to reduce the number of insecure entry points into the products. We’ve replaced this way of exchanging information between Atlassian products with more secure solutions that follow industry best practices, like the OAuth 2.0 protocol.

Before you upgrade to Jira 11.0

Check the compatibility of your Marketplace apps

As a major release, Jira 11.0 introduces backward-incompatible changes to the apps' API. If you build custom in-house apps, you need to test their compatibility and update them.

If you have installed apps from the Atlassian marketplace or another source, you also need to check their compatibility and update them before performing the upgrade. To check app compatibility, visit Checking app compatibility with application updates or the Atlassian Marketplace to see if your app hosting is compatible with your product version.

Resolved issues

See the full list of the issues we’ve resolved throughout the lifecycle of Jira Software 11.0.