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.
Starting from Jira Data Center 10.0.0, asynchronous webhooks are now the default and only option. This update significantly improves the user experience by processing webhooks through a dedicated thread pool, rather than tying them to the user request. Previously, in Jira 9 and earlier, webhooks were processed synchronously, with the most computationally intensive work performed during the HTTP request.
Environments with exceptional webhook usage in both Jira 9 and 10 might exceed the guardrails set by the default parameters. You can customize these limits to better suit your organization’s needs. We recommend testing the asynchronous webhooks within your staging environments before a final upgrade. If you experience any issues, check our list of known problems or reach out to our support team.
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-m0001.
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 10.6 release notes and Jira Service Management 10.6 release notes.
Download Jira Software 10.6 and Jira Service Management 10.6.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 10.6 and Jira Service Management 10.6. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.6.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.6.0-m0003.
This EAP release isn't for production or demonstration use.
As part of replacing Lucene-specific APIs in Jira with index-agnostic Search APIs, the deprecated APIs have been annotated with @com.atlassian.jira.search.annotations.DeprecatedBySearchApi.
To help identify usages of these deprecated APIs in your application, we've developed an OpenRewrite recipe available at OpenRewrite Search API Recipes. These recipes were developed as an experimental internal tool. We're releasing them as a courtesy to our partners, as we've seen great success using them ourselves.
Explore how to use OpenRewrite to identify Search API migrations
We'll make best-effort attempts to address any problems you might encounter, but these recipes don't have an official support status.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 10.6 and Jira Service Management 10.6. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.6.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.6.0-m0001.
This EAP release isn't for production or demonstration use.
We’ve changed the order of properties in the Sprint custom field. So far, the properties in the Sprint custom field were ordered starting with id, rapidViewId, and state. With the latest Jira Software Long Term Support (LTS) 10.3.4, these properties are listed alphabetically by property name, starting with activatedDate, autoStartStop, and completeDate. This change standardizes the property order and improves consistency across API responses.
This change might affect scripts or integrations that rely on the previous order of properties. To avoid potential issues, we recommend updating your script to parse key/value pairs instead of relying on the position of keys.
For example, in Jira 9.12.14, the Sprint field content starts with id and is followed by rapidviewId, state, name, startDate, endDate, completeDate, activatedDate, sequence, goal, synced, autoStartStop, and incompleteIssuesDestinationId. See the line 12 in the code below.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
jmon@GPF1W9J4WD ~ % curl -u admin:jira -X GET "http://localhost:41214/j91214/rest/api/latest/issue/SP-2?fields=customfield_10108" | python3 -mjson.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 558 0 558 0 0 3657 0 --:--:-- --:--:-- --:--:-- 3671
{
"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",
"id": "10042",
"self": "http://localhost:41214/j91214/rest/api/latest/issue/10042",
"key": "SP-2",
"fields": {
"customfield_10108": [
"com.atlassian.greenhopper.service.sprint.Sprint@2faec734[id=13,rapidViewId=1,state=FUTURE,name=Sample Sprint 2025-02-27,startDate=2025-02-27T22:02:00.000-08:00,endDate=2025-03-27T22:02:00.000-07:00,completeDate=<null>,activatedDate=<null>,sequence=13,goal=My Goal,synced=false,autoStartStop=false,incompleteIssuesDestinationId=<null>]"
]
}
}Starting from Jira 10.3.4, the properties are ordered alphabetically. The first property is activatedDate followed by autoStartStop, completeDate, endDate, goal, id, incompleteIssuesDestinationId, name, rapidViewId, sequence, startDate, state, and synced. See the line 12 in the code below.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
curl -u admin:sphere -X GET "https://linux-94430.prod.atl-cd.net/jira/rest/api/latest/issue/SCRUM-10?fields=customfield_10100" | python3 -mjson.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 591 0 591 0 0 1680 0 --:--:-- --:--:-- --:--:-- 1683
{
"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",
"id": "10009",
"self": "https://linux-94430.prod.atl-cd.net/jira/rest/api/latest/issue/10009",
"key": "SCRUM-10",
"fields": {
"customfield_10100": [
"com.atlassian.greenhopper.service.sprint.Sprint@37817076[activatedDate=2021-03-24T02:51:06.809Z,autoStartStop=false,completeDate=<null>,endDate=2021-04-07T03:11:06.809Z,goal=<null>,id=1,incompleteIssuesDestinationId=<null>,name=Sample Sprint 2,rapidViewId=1,sequence=1,startDate=2021-03-24T02:51:06.809Z,state=ACTIVE,synced=false]"
]
},
"renderedFields": null
} We’re happy to present the release of Jira Software and Jira Service Management 10.5. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 10.5 release notes and Jira Service Management 10.5 release notes.
Download Jira Software 10.5 and Jira Service Management 10.5.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 10.5 and Jira Service Management 10.5. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.5.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.5.0-m0003.
This EAP release isn't for production or demonstration use.
We’re happy to present the first Early Access Program (EAP) builds of Jira Software 10.5 and Jira Service Management 10.5. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.5.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.5.0-m0001.
This EAP release isn't for production or demonstration use.
We have recently noticed an unusual increase in API usage. In order to maintain reliable services for both Atlassian customers and partners, we will begin enforcing more granular rate limits for Confluence and Jira APIs.
We will begin enforcing REST API (Quota and Burst based) rate limits for all free apps on or after August 18, 2025. We have added additional headers to provide further transparency. Please monitor header responses to see where you are at with regard to limits.
In some circumstances where apps are highly impacting the stability of our platform, we reserve the right to enforce the limits at an earlier date. We will notify your listed contact via email if you are impacted. Additionally, we are planning to bring clarity to rate limits across our platform infrastructure over the next year, including paid apps.
We recommend all customers and partners ensure they're not exceeding the rate limits so that they do not get impacted at a later date.
Learn more about the header responses and read relevant FAQs about rate limiting adjustments for Jira here and Confluence here.
To maintain high security standards, we're making the following changes to the upcoming major versions of all the Data Center products:
Spring and Jakarta upgrade
JQuery upgrade
Removal of deprecated components in AUI 10
Removal of Trusted apps
End of support for LESS
End of support for the Original theme
Supported platform updates
Visit the https://developer.atlassian.com/platform/marketplace/dc-apps-platform-8/#prepare-your-data-center-app-for-2025-security-and-usability-updates page to learn more about these updates, find resources, useful dates, and links.
As announced last year, we’re working on enabling OpenSearch as an opt-in feature. We’ve laid the foundations with the new Jira search API. This API aims to provide a comprehensive common and efficient index and search access method, effectively addressing the limitations of the current Lucene index access methods.
If your apps use Lucene search and index access directly, ensure their migration to the new search API because the older Lucene-specific methods are deprecated in Jira Data Center 10.4 and will be removed in future.
This release marks the first milestone of our larger purpose aimed at replacing the Lucene-based indexing process with OpenSearch for customers choosing to do so.
Read the Jira search API upgrade notes for important info on the new search and index access methods.
Join the conversation on this Atlassian Developer Community thread.
We’re happy to present the release of Jira Software and Jira Service Management 10.4. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 10.4 release notes and Jira Service Management 10.4 release notes.
Download Jira Software 10.4 and Jira Service Management 10.4.
We’re happy to present the last Early Access Program (EAP) build of Jira Software 10.4 and Jira Service Management 10.4. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.4.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.4.0-m0004.
This EAP release isn't for production or demonstration use.
Rate this page: