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.
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.
EAP 06 is the final EAP for Jira 11.
We’re happy to present the sixth and final Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0015.
This EAP release isn't for production or demonstration use.
We’re happy to present the fifth Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0012.
This EAP release isn't for production or demonstration use.
We’re sharing a guide that explains how to improve page load by managing Web Resource Manager (WRM) and Custom App Dependencies.
In Jira, WRM is responsible for preparing JavaScript and CSS resources for specific pages to ensure apps function correctly. When creating an app, you define its dependencies in <web-resource> and specify the context where your app will run in Jira. Then, WRM generates batch.js and batch.css files by collating all required dependencies for apps running in that context.
Depending on the context registry and how dependencies are defined, these batch files can become very large, leading to slow page load performance. However, you can improve the page load by:
Code splitting
Deferring script loading
Compressing files
Further optimization for custom apps
We’re happy to present the third Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.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.7. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 10.7 release notes and Jira Service Management 10.7 release notes.
Download Jira Software 10.7 and Jira Service Management 10.7.
We've published two new guides to help you move on from Lucene to Search API:
To provide you with more options for search tooling, we're introducing an abstraction layer to Jira's search functionality. By removing Lucene from Jira's public API and exposing search operations through this new API, Jira can now support multiple underlying search platforms, such as Lucene and OpenSearch. The Search API maintains a similar data structure and search operations as previously available in Jira, but with some key differences. Explore how to migrate from Lucene to Search API
Starting with Jira 11, you can no longer iterate through search results using the Lucene-specific org.apache.lucene.search.Collector. Instead, the Search API now provides several platform-agnostic alternatives: Search, Aggregation, and Search Stream. Explore our migration guide for Lucene collectors
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0002.
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 10.7 and Jira Service Management 10.7. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.7.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.7.0-m0004.
This EAP release isn't for production or demonstration use.
We’re happy to present the first Early Access Program (EAP) build of Jira Software 10.7 and Jira Service Management 10.7. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.7.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.7.0-m0002.
This EAP release isn't for production or demonstration use.
Rate this page: