This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira Software Data Center 11.1 and Jira Service Management Data Center 11.1.

Latest version

Here you can find information about the latest EAPs.

Summary of changes

This section provides an overview of the changes we intend to make so that you can start thinking about their impact on your apps. Once the updates are ready, we'll indicate when they’ve been implemented and in which milestone.

• Jira Software and Jira Service Management common features
  • Manage your integrations and automations with service accounts
  • Sign SAML authentication requests 
  • React 18.3 and Atlaskit upgrade
• Jira Software features
  
  • Find missing issues in Advanced Roadmaps for Jira 
• Jira Service Management features
  
  • Lucene removed from canned responses
  • Faster scrolling on the customer page
  • Limit object traversal in Assets 
  • UI updates in Assets

Jira Software and Jira Service Management common features

Manage your integrations and automations with service accounts

Status: IMPLEMENTED (EAP 01)

We’re introducing service accounts to Data Center products. Service accounts are specialized, non-user accounts created for secure and efficient management of automated processes and external integrations. With service accounts, you can use OAuth 2.0 authentication to access REST APIs, run scripts, and perform tasks securely.

Sign SAML authentication requests 

Status: IMPLEMENTED (EAP 01)

We’re implementing sign SAML authentication requests to strengthen your instance’s security. When SAML is enabled, the authentication plugin generates a certificate and private key during startup. The private key signs SAML authentication requests, and you can download the certificate to upload to your Identity Provider (IdP). This lets the IdP verify the authenticity and integrity of each request.

To enable signing SAML authentication requests, go to the Authentication methods page and select Sign requests.

React 18.3 and Atlaskit upgrade

Status: IMPLEMENTED (EAP 02)

We're upgrading Jira Data Center to use React 18.3 and the latest Atlaskit components. This update helps keep your instance secure and compliant by enabling continuous security updates and bug fixes from Atlaskit and React. In Jira 11.1, we upgrade Platform packages, Jira Service Management, and Assets.

The React 16 web resources exposed by Jira are now deprecated. We recommend migrating your custom apps and integrations to React 18.3 to ensure compatibility and continued support. Review code sharing and migration guidance

Jira Software features

Find missing issues in Advanced Roadmaps for Jira 

Status: IMPLEMENTED (EAP 01)

The new In-Product Diagnostics (IPD) feature helps you quickly understand why a specific issue isn’t visible in your Advanced Roadmaps for Jira dashboard. You can search for any issue by its key, and IPD will analyze your dashboard’s filters and settings to explain why the issue is missing.

Diagnostics run in the background, and the results are stored briefly for fast access. Each request is handled separately, and rate limits keep performance steady.

Jira Service Management features

Lucene removed from canned responses

Status: IMPLEMENTED (EAP 01)

We are removing the Lucene dependency from canned responses to improve performance, especially as the number of canned responses increases in larger instances.

With this change, searches for canned responses now match titles and content directly in the database. Lucene’s relevance scoring is no longer available, but results are still sorted by usage and last updated date.

The new database search is enabled by default with the feature flag sd.canned.responses.search.sql.disabled. If you need to revert to Lucene indexing, you can disable the feature flag. Keep in mind that Lucene indexes might be outdated, so you’ll need to restart your instance, perform a full reindex, or reindex canned responses using the following API endpoint: /rest/servicedesk/canned-responses/1/index/reindex-all.

Faster scrolling on the customer page

Status: IMPLEMENTED (EAP 01)

The customer page now loads much faster, thanks to a new scroll-based pagination experience. Previously, this page could take several minutes to display all customers, especially in large instances. With this update, you can quickly browse customers as you scroll, without waiting for the entire list to load.

No functionality has been removed—page state was not stored in the URL before, so the workflow remains unchanged.

Limit object traversal in Assets 

Status: IMPLEMENTED (EAP 02)

We've introduced a limit on the number of Assets objects that can be traversed (visited through object reference attributes) in a single request. This limit helps prevent Jira from running out of memory and crashing.

By default, the traversal limit is 100,000 objects. A request that traverses this many objects is expected to use about 500MB of memory. You can adjust the limit on the Assets configuration page in the admin settings. To disable traversing entirely, set the limit to 0. However, disabling the limit may expose your instance to out-of-memory errors.

This update applies to the /rest/insight/1.0/iql/objects and /rest/insight/1.0/aql/objects endpoints.

UI updates in Assets

Status: IMPLEMENTED (EAP 02)

As part of ongoing UI component improvements, we’re introducing a series of updates to Assets UI. These changes don’t affect functionality and are focused on usability and accessibility improvements.

We’re updating the following areas:

• Share these results modal for Assets searches
• Edit color theme pop-up
• Upload icon window
• screens for creating and editing objects
• DateTime field
• Assets details view and banner layout
• comments
• Attachments and Comments buttons
• Print QR Code pop-up
• Delete confirmation pop-up
• References tab
• Add attachment dialog
• Print label modal
• search view
• bulk action messages
• Report Manager view
• reports share options