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

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
  • Supported platform changes
  • End of support for LESS
  • End of support for the Original theme
  • Removal of jQuery 2 migrate
  • App signing is now enabled by default
  • Preparing for OpenSearch (EAP 02)
  • Spring and Jakarta upgrade (EAP 02)
  • Updated Tomcat protocols (EAP 02)
  • New REST endpoint for listing users (EAP 04)
  • Removal of a deprecated component (EAP 04)
  • Data fields updates (EAP 04)
  • Sorting on TEXT entity property (EAP 04)
  • Invisible field values no longer stored (EAP 04)
  • Change history index prefixes (EAP 04)
  • Removal of Trusted apps (EAP 04)
  • Global serialization filter (EAP 05)
  • Removal of deprecated components in AUI 10 (EAP 05)
  • Add scopes to REST endpoints to use OAuth 2.0 2LO (EAP 05)
  • Basic authentication disabled by default (EAP 05)
  • Simplification of multipart handling in WebWork (EAP 05)
• Jira Software features
  • New look and feel for Advanced Roadmaps for Jira 
  • Removal of the deprecated Text gadget (EAP 02)
  • View your repo health with Sync history (EAP 02)
  • Removal of avatar endpoints (EAP 05)
  • Introducing the Jira Data Center connector for Rovo (EAP 05)
• Jira Service Management features
  • Changed sorting behavior for custom fields

Jira Software and Jira Service Management common features

Supported platform changes

Status: IMPLEMENTED (EAP 01)

In Jira 11, we’ve removed support for:

• JDK 17
• PostgreSQL 15
• PostgreSQL 14
• PostgreSQL 13
• PostgreSQL 12
• MySQL 8.0
• Oracle 18c
• MSSQL Server 2017

And we’ve added support for:

• JDK 21
• PostgreSQL 17
• MySQL 8.4 LTS

This version of Jira will only run on Java 21.

End of support for LESS

Status: IMPLEMENTED (EAP 01)

To enhance the security, performance, and overall developer experience, we’re deprecating both the LESS web-resource transformer and the LESS Maven plugin.

We’re updating Look and Feel to use CSS variables, and all styles will either be CSS or compiled to CSS at build-time. We’re also removing LESS compilation from Java build and runtime. You can continue to use LESS or any other CSS pre-processor at build-time.

We recommend you replace the runtime transformation of LESS files with build-time compilation or move to native CSS altogether where applicable.

End of support for the Original theme

Status: IMPLEMENTED (EAP 01)

With the new light and dark themes that brought accessibility and usability improvements, we’ve removed the original theme from the theme switcher and will fully remove it in Jira 11.

Removal of jQuery 2 migrate

Status: IMPLEMENTED (EAP 01)

We’ve removed the jQuery 2 migrate plugin and plan to upgrade to jQuery 3 in the next EAPs to align on jQuery versions across all Data Center products. This means a significant jQuery version uplift for products containing older versions of jQuery that will make developing cross-product apps easier.

App signing is now enabled by default

Status: IMPLEMENTED (EAP 01)

As we communicated in February, in 2025 we’re rolling out app signing. In this release, app signing is enabled by default. This feature enables better security and increases customer trust in what they install on their local instances.

If you upload your apps to Atlassian Marketplace, we’ve got you covered. Once Marketplace validates and approves your app, Atlassian will sign and trust all your apps by default; no additional action is needed. App signing affects only new app installations, previously installed apps will not undergo verification.

For details on private builds, check this CDAC post.

Preparing for OpenSearch

Status: IMPLEMENTED (EAP 02)

We're laying the foundations for more agnostic option for search tooling, starting with adding an abstraction layer. This change is key to enable future OpenSearch support. The new abstraction layer introduces a new search API. Search and indexing performance will remain consistent with the existing Lucene implementation. For more details, check the following articles:

• Search API deprecations and upgrade guide for Jira 11
• Migrating FieldIndexers in Jira 11

Spring and Jakarta upgrade

Status: IMPLEMENTED (EAP 02)

To maintain high security standards and keep dependencies supported and up to date, we’re updating Spring to the 6.x line. Spring 6 is no longer compatible with the currently used Jakarta 8, requiring us to also update the Jakarta version to EE Platform 10, specifically:

• Jakarta Servlet 6.0
• Jakarta RESTful Web Services 3.1
• Jakarta Dependency Injection 2.0
• Jakarta Annotations 2.1
• Jakarta Activation 2.1
• Jakarta Mail 2.1
• Jakarta XML Binding 4.0
• Jakarta Bean Validation 3.0

We’re also updating all the other libraries that depend on Spring and Jakarta.

We won’t be making any changes to the Atlassian API unless they’re necessary because of the updates to the Jakarta API. There are also several API changes in Jakarta that may impact apps.

Known issues

Here are some known issues you might encounter after the upgrade. We’re actively working on solving them:

•  The following plugins don’t start:
  • Jira DVCS Connector Plugin (com.atlassian.jira.plugins.jira-bitbucket-connector-plugin)
  • Atlassian Troubleshooting and Support Tools (com.atlassian.troubleshooting.plugin-jira)
  • Jira Cloud Migration Assistant (com.atlassian.jira.migration.jira-migration-plugin)
  • Atlassian Jira - Plugins - ATST Health Checks (com.atlassian.jira.jira-atst-healthcheck-plugin)
• After Jira startup, you must manually enable the software application in Administration, then Manage apps. The software application sometimes stops working and needs to be re-enabled in Administration, then Manage apps.
• The Releases, Reports, and Components pages aren’t working.
• Issues/current search isn’t working, but Issues/search for issues is working.

Updated Tomcat protocols

Status: IMPLEMENTED (EAP 02)

We’ve updated the protocols provided by Jira extending the Tomcat protocols with support for password encryption:

New REST endpoint for listing users

Status: IMPLEMENTED (EAP 04)

We’re introducing a new endpoint for listing users: https://{baseurl}/rest/api/2/user/list.

Removal of a deprecated component

Status: IMPLEMENTED (EAP 04)

We’re removing the following non-API component: com.atlassian.jira.com.rproxy.goskope.component.pico.ComponentManager.

Date fields updates

Status: IMPLEMENTED BREAKING UI CHANGES (EAP 04)

LocalDate is now stored as milliseconds since epoch instead of days since epoch. The impacted fields are due date, work log date, and custom date picker. This change will be transparent for data access through the search API.

Sorting on TEXT entity property

Status: IMPLEMENTED BREAKING UI CHANGES (EAP 04)

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.

Invisible field values no longer stored

Status: IMPLEMENTED (EAP 04)

In previous versions, invisible fields weren’t indexed, they were stored only. In Jira 11, we stopped storing values for such fields, meaning the field value isn’t processed at all if invisible.

Padded string fields for number custom fields are also not stored anymore. Those fields now look like string_customfield_xxxxx.

Change history index prefixes

Status: IMPLEMENTED BREAKING UI CHANGES (EAP 04)

Change history data is indexed to a Lucene index located at {jira-home}/caches/indexesV2/changes. Currently, the index fields are named with prefixes that correspond to the Jira fields affected by the change history.

For example, change history that contains assignee and priority fields is indexed to a document that looks like the following snippet:

In Jira 11, we no longer prefix the names of the index fields. Instead, we prefix the values. With the new structure, the document from the example above will now look like this:

If your app currently uses the change history index (for instance, to search historical changes), you’ll need to make adjustments to your queries to reflect this new data structure.

 Removal of Trusted apps

Status: IMPLEMENTED (EAP 04)

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.

Global serialization filter

Status: IMPLEMENTED (EAP 05)

We’re implementing a global serialization filter that relies on a central blocklist for Java deserialization, Velocity, and XStream. This filter is designed to block specific classes and patterns that are recognized as vulnerable to Remote Code Execution (RCE) through publicly known gadget chains.

Removal of deprecated components in AUI 10

Status: IMPLEMENTED (EAP 05)

We’re removing some outdated AUI 10 components with design and accessibility issues. Make sure to move to their new versions or migrate to Atlaskit:

• Dropdown 1 - replaced by Dropdown 2
• Toolbar 1 - replaced by Toolbar 2

We’re also upgrading some outdated dependencies:

• npm: dompurify upgraded from 2.5.7 to 3.1.6+. This dependency is used internally on the tooltip titles. Don’t reuse the version under the hood.
• npm: jquery-form upgraded from 2.67 to 4.3.0+. This upgrade will ensure better jQuery 3 compatibility.

We’re also deprecating or removing the following:

• Template - AUI Documentation - we’re moving to Soy or the I18n system as appropriate. This is so we can better support fewer languages with tools and prevent security issues from arising from a homebrewed templating language.
• Dark mode (old) - AUI Documentation - we’re removing the old unused dark theme since we’ve introduced a new one. If you’ve followed our recent guide (Prepare your Data Center app for the dark theme) to prepare for dark theme by using design tokens, you should be all set.
• Original theme - since the “light” theme is replacing it, all the fallback values will be gone.
• Redundant polyfills that are now natively supported in browsers, for example npm: css.escape, custom events, and the <input> placeholder.
• npm: @atlassian/tipsy - this is no longer maintained and the AUI library stopped using it internally from version 9.3. You can bundle it if you wish, but we recommend moving to Floating UI - Create tooltips, popovers, dropdowns, and more or using Atlaskit or AUI components where possible.
• npm: trim-extra-html-whitespace - this is no longer maintained and only used internally in our public documentation. This shouldn’t be needed in the browser. You can bundle it if you wish, but we recommend finding a maintained HTML minifier.
• Low-usage and renamed Soy templates, web-resources, and CSS classes.

Other changes include the Node 22 engine requirement. This will only affect using AUI via NPM, not through the running product.

Add scopes to REST endpoints to use OAuth 2.0 2LO

Status: IMPLEMENTED (EAP 05)

We’ve introduced @ScopesAllowed to improve security and control over REST endpoints.

Add the @ScopesAllowed annotation to your endpoints to make them accessible using an OAuth 2.0 Client Credentials token (2LO). For example, this annotation requires that the access token has the WRITE scope before providing access to this endpoint.

@POST
@ScopesAllowed(requiredScope = "WRITE")
public void createEntity(...) {}

Explore Jira OAuth 2.0 scopes for incoming links

Basic authentication disabled by default

Status: IMPLEMENTED (EAP 05)

We’re disabling authentication with basic authentication by default. This is a first step towards the removal of basic authentication altogether as we develop and mature alternatives to support the remaining few use cases.

Simplification of multipart handling in WebWork

Status: IMPLEMENTED (EAP 05)

We've removed the following classes from Jira and WebWork that were no longer used by Jira and weren’t intended for use by apps. If your app relies on these classes, you'll need to transition to alternatives.

com.atlassian.jira.web.TempFileRemovingMultipartRequestWrapper
webwork.multipart.PellMultiPartRequest

Jira Software features

New look and feel for Advanced Roadmaps for Jira

Status: IMPLEMENTED BREAKING UI CHANGES (EAP 01)

We're rolling out major updates to the user interface in the Advanced Roadmaps for Jira. These enhancements provide a seamless experience across Programs and Plans, ensuring consistency in how you view and manage your projects.

Here’s what's new:

• Restructured user interface and improved administration and program management functionalities for a more intuitive experience.
• Implemented dark theme, offering a modern and visually appealing interface. To test your apps for compatibility, enable the dark theme by going to your Profile, then Theme, and select Dark.

With these changes, we've also addressed security and accessibility concerns and reduced technical debt by updating outdated technologies.

We’ve also implemented these changes in the upcoming Jira 10.7 that will be released before Jira 11.0.

Removal of the deprecated Text gadget

Status: IMPLEMENTED (EAP 02)

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.

View your repo health with Sync history

Status: IMPLEMENTED (EAP 02)

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.

Removal of avatar endpoints

Status: IMPLEMENTED (EAP 05)

We’ve removed the following endpoints:

• /rest/api/2/avatar/{type}/temporary
• /rest/api/2/avatar/{type}/temporaryCrop

Instead, use the following, existing alternatives:

• /rest/api/2/universal_avatar/type/{type}/owner/{owningObjectId}/temp
• /rest/api/2/universal_avatar/type/{type}/owner/{owningObjectId}/avatar

Introducing the Jira Data Center connector for Rovo

Status: IMPLEMENTED (EAP 05)

The Jira Data Center connector facilitates seamless data synchronization from Jira Data Center to Rovo in Atlassian Cloud, allowing you to leverage Cloud-based AI capabilities without requiring a full migration to the 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.

If you already have access to Rovo, refer to this guide for step-by-step instructions on setting up the connector.

Jira Service Management features

Changed sorting behavior for custom fields

Status: IMPLEMENTED (EAP 01)

We’ve changed the sorting behavior for Assets and Organizations custom fields that support multiple values. Previously, all values were concatenated for comparison, but now only the smallest value is used which might change the order your items.

This change enhances sorting accuracy and consistency and affects the following custom fields:

• Assets object
• Assets readonly object
• Assets object (multiple) (legacy)
• Assets referenced object (multiple)
• Organizations