Starting from Jira 10.1, we've moved the communication about Jira Software Data Center and Jira Service Management Data Center development releases to the Jira development releases page. With this transition, we aim to provide you with a single source of information about 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 the availability of upcoming Jira Data Center releases.
We’re happy to present the release of Jira Software and Jira Service Management 11.3. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.3 release notes and Jira Service Management 11.3 release notes.
Download Jira Software 11.3 and Jira Service Management 11.3.
Starting with the following versions, major product releases will no longer support installing plugins that require transformation:
Confluence 11.0
Jira Software 12.0
Jira Service Management 12.0
Bamboo 13.0
Bitbucket 11.0
Crowd 8.0
For details, explore Transformed to transformerless plugin conversion.
Context:
Any P2 plugin development using modern versions of Atlaskit will end up compiled-css.css files inside target/classes. We’ve been upgrading React & Atlaskit in the DC products and so many of the P2 plugins that make up our products now have a compiled-css.css file.
This made a long-standing bug with local development more obvious. The first compiled-css.css file found by the plugin system was used for all P2 plugins (instead of using the specific file from the respective plugin). https://compiledcssinjs.com/ compiles equivalent styles to the same CSS classname and there is decent, but not perfect overlap in styles. The result was that often just one Atlaskit component wouldn’t render correctly or any plugin-specific styles would be missing. This can be quite hard to debug because in the browser development tools it looks like the compiled-css.css file doesn’t change no matter what you do, this is of course because it’s using another plugins'.
Action:
We have fixed this long-standing underlying bug, but remained backwards compatible. To use the new, fixed local development system instead of the existing, buggy implementation you will need to use the upcoming post-2025-LTS product versions for local development (e.g. Confluence 10.3, e.g. Jira 11.4), and also upgrade QuickReload to 6.2.0+ (included in AMPS 9.7.2). If everything goes smoothly we will consider backporting to LTS releases of the products. Note: Crowd doesn’t have LTS releases, but it’s looking to be in Crowd 7.3
For more details read the original bug report: https://ecosystem.atlassian.net/browse/PLUG-981.
If you have any issues or questions, feel free to ask us on developer community.
Cheers,
Michael Kemp
We’re sharing a guide that explains the benefits of using OpenSearch as an alternative to the default Lucene search platform in Jira Data Center. By using OpenSearch instead of Lucene, you’ll be able to speed up you Jira, reduce the number of required Jira nodes and use cheaper hardware.
The guide covers:
Key differences between OpenSearch and Lucene.
Benchmark results that show OpenSearch delivers faster search and better scalability.
Guidance on when and why to switch, with further configuration steps.
OpenSearch in Jira
OpenSearch in Jira isn’t just about searching — it supports everything you do, from loading boards and viewing backlogs to generating reports and working with issues. Because so many core actions rely on search, OpenSearch’s speed, consistency, and reliability have a direct impact on your team’s productivity and experience. Discover our hardware recommendations for OpenSearch
We’re happy to present the first Early Access Program (EAP) build of Jira Software 11.3 and Jira Service Management 11.3. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.3.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.3.0-m0002.
This EAP release isn't for production or demonstration use.
We’re happy to present the release of Jira Software and Jira Service Management 11.2. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.2 release notes and Jira Service Management 11.2 release notes.
Download Jira Software 11.2 and Jira Service Management 11.2.
You can now connect Jira Product Discovery ideas with delivery items on remote Cloud or Data Center instances linked to your Jira Product Discovery site. After setup, a new “site” field appears, letting you choose whether to create or link a delivery item locally or remotely. This integration keeps delivery progress in sync across your Cloud sites and Data Center instances, so you no longer need to update items manually on each platform. You’ll always see up-to-date insights about delivery progress from all linked items.
This integration requires Jira Data Center version 10.3 or higher, a free Marketplace app, and a Jira Product Discovery Premium plan. There are no additional edition requirements for connecting to a remote Cloud instance.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.2 and Jira Service Management 11.2. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.2.
In this EAP, we’ve marked the Instance optimizer safeguards as breaking change. More about safeguards breaking changes
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.2.0-m0041.
This EAP release isn't for production or demonstration use.
We’re happy to present the Early Access Program (EAP) build of Jira Software 11.2 and Jira Service Management 11.2. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.2.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.2.0-m0040.
This EAP release isn't for production or demonstration use.
As Jira instances grow in size and scale, the default search engine, Lucene, may be slower to index and return search results. To address this, Jira Data Center now offers an alternative search engine as an opt-in feature — OpenSearch
The second early access program (EAP) of OpenSearch for Jira gives you an opportunity to test apps' compatibility with OpenSearch. More about OpenSearch for Jira EAP02
We've implemented the following changes in the EAP02:
Full sorting support
Label auto-complete
Resilient indexing
Fast re-indexing
Read-your-write consistency
Support for all indexing languages
The total results count for boards and backlogs in OpenSearch is capped at 10,000 by default. More about 10,000 issue display limit for boards and backlogs
You can increase this limit by following the steps in the workaround for unbounded queries.
We’re happy to present the release of Jira Software and Jira Service Management 11.1. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.1 release notes and Jira Service Management 11.1 release notes.
Download Jira Software 11.1 and Jira Service Management 11.1.
Trusted apps authentication has been removed. For details, see Removal of Trusted apps.
A supported migration path is available via OAuth 1 with impersonation.
Details
OAuth 1 with impersonation allows plugins to generate signed HTTP requests back to the same Data Center instance while impersonating a specific user.
Relevant ticket: CONFSERVER-99078 – Java API for authenticated HTTP requests to current Confluence instance.
A demo plugin illustrates how to implement OAuth 1 with impersonation for both Jira and Confluence: https://bitbucket.org/atlassian/dc-platform/src/4407b6ea004529ba93a69315d99765657ce7829b/demos/oauth1-impersonation-plugin-example/?at=release%2F8.0.x.
OAuth 1 with impersonation is already part of the existing OAuth 1 plugin.
Product Changes
Jira 11.0.1 (released) and Confluence 10.0.4 (scheduled for release) now automatically create a host consumer provider on the product side, enabling plugins to connect back to the same Data Center instance.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.1 and Jira Service Management 11.1. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.1.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.1.0-m0012.
This EAP release isn't for production or demonstration use.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.1 and Jira Service Management 11.1. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.1.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.1.0-m0011.
This EAP release isn't for production or demonstration use.
We’re happy to present the release of Jira Software and Jira Service Management 10.6. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.0 release notes and Jira Service Management 11.0 release notes.
Download Jira Software 11.0 and Jira Service Management 11.0.
Rate this page: