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 first Early Access Program (EAP) build of Jira Software 10.2 and Jira Service Management 10.2. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.2.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.1.0-m0003.
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.1 and Jira Service Management 10.1. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.1.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.1.0-m0003.
This EAP release isn't for production or demonstration use.
We’re making preparations to introduce OpenSearch as an opt-in feature for our customers in a future Jira Data Center release. With OpenSearch, we’re aiming to externalize indexing processes to support large customers in improving performance for their search- and index-related functions in Jira DC.
Starting from Jira 11, we will stop providing Lucene as a dependency and we’ll keep you informed about future deprecations.
This project has only just begun, so we don’t yet have a timeline. We wanted to give you as much advance notice about this feature as possible, and we’ll share a guide to help you migrate and test your apps as soon as it’s ready.
Join the conversation on this Atlassian Developer Community thread.
We’re happy to present the first Early Access Program (EAP) build of Jira Software 10.1 and Jira Service Management 10.1. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.1.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.1.0-m0001.
This EAP release isn't for production or demonstration use.
We’re happy to present Jira Software 10.0 and Jira Service Management 10.0. Find out what’s included in this version in the Jira Software release notes and Jira Service Management release notes.
We’re happy to present the Release Candidate (RC) build of Jira Software 10.0 and Jira Service Management 10.0.
You can download the Release Candidate from this page. If you’re using maven.atlassian.com, the version is 10.0.0-m0011.
If you’d like to share your feedback, leave a reply in the Atlassian Developer Community thread.
This release is not for production or demonstration use.
This is the only planned Release Candidate for Jira Software 10.0 and Jira Service Management 10.0. Next, you can expect the General Availability (GA) release.
We’re happy to present another Early Access Program (EAP) build of Jira Software 10.0 and Jira Service Management 10.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira Software 10.0 and Jira Service Management 10.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.0.0-m0010.
If you’d like to share your feedback, leave a reply in the Atlassian Developer Community thread.
This EAP release is not for production or demonstration use.
Make sure to delete secrets-config.yaml before upgrading your current Jira version to EAP07 or EAP08 because of a file format change. When you upgrade, the file will be recreated automatically with the new format.
This is the last EAP release of Jira Software 10.0 and Jira Service Management 10.0. Next, you can expect the release candidate (RC) which is close to being ready for the final release but may still undergo changes before the final version is out.
atlassian-renderer has been upgraded to 9.0.3
We’ve removed some REST API endpoints in the EAP 03 release of Jira Service Management 10.
The More details section lists the REST API endpoints we’ve removed.
Change | Instructions |
|---|---|
Removed | Use |
Removed
| Use |
Removed | Use |
Removed | Use |
Removed | Use |
We’re happy to present another Early Access Program (EAP) build of Jira Software 10.0 and Jira Service Management 10.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira Software 10.0 and Jira Service Management 10.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.0.0-m0009.
If you’d like to share your feedback, leave a reply in the Atlassian Developer Community thread.
This EAP release is not for production or demonstration use.
The next EAP release of Jira Software 10.0 and Jira Service Management 10.0 won’t bring any further functional or technical changes as Platform 7 integration closed the planned scope. We’ll focus on quality aspects and ensuring further system stability instead.
We’ve modernized the look and feel of our Jira Software Data Center REST API and Jira Service Management Data Center REST API documentation by migrating it to Swagger. In addition to the refreshed look and feel we’re getting from the Swagger API documentation framework, this migration will make our API docs easier for you to navigate, find examples, and copy snippets from.
In this EAP release, we’re introducing some Java API breaking changes.
The More details section lists the breaking changes.
Change | Instructions |
|---|---|
We’re removing
The same change
Same with | Serialize the value before passing it to the method and deserialize after reading it. |
| Use the new type in method calls. |
| Replaced class is equivalent. |
Midway through this quarter, we’ll be adding new Data Center app scanners to our suite of scanners (Ecoscanner) that scans Data Center apps listed on the Marketplace.
Here is what we’ll be scanning for:
Use of hardcoded secrets in Marketplace Data Center apps
Potential malware in Marketplace Data Center apps
To expand on this, the new DC app scanners will include:
Secret scanner: The new secret scanner will look for any hard-coded secrets in DC apps that could potentially pose a security risk if exposed. We engineered the scanner to detect secrets and manage potential security risks, ensuring that customer data remains protected from unauthorized access.
Malware scanner: Atlassian has implemented a robust malware scanning system for all Data Center applications in the Marketplace. This scan aims to identify and mitigate potential malware threats, thereby enhancing the security and integrity of our DC applications.
If a risk is detected: Atlassian will alert the app developer so they may investigate. If there is a critical risk, we recommend that Marketplace Partners notify customers.
We won’t begin issuing these new tickets to partners at this time; this is a preliminary announcement and an opportunity for partners to prepare. Atlassian plans on issuing tickets after August 15th 2024 via the AMS Jira project.
We are committed to working collaboratively with partners to continue improving the security of our Marketplace and fostering trust with our customers.
Partners with Partner Portal access can view the announcement in the Partner Portal blog.
We’re happy to present another Early Access Program (EAP) build of Jira Software 10.0 and Jira Service Management 10.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira Software 10.0 and Jira Service Management 10.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.0.0-m0008.
If you’d like to share your feedback, leave a reply in the Atlassian Developer Community thread.
This EAP release is not for production or demonstration use.
The next EAP release of Jira Software 10.0 and Jira Service Management 10.0 won’t bring any further functional or technical changes as Platform 7 integration closed the planned scope. We’ll focus on quality aspects and ensuring further system stability instead.
App usage page issue is fixed resolved
The error when accessing dashboard on Jira Activity Stream Gadget is fixed
Disabled debug mode for velocity method allowlist to check the completeness of the list - https://developer.atlassian.com/server/framework/atlassian-sdk/configuring-the-velocity-allowlist/ (if you think that your method is blocked, then look for the following log: Invocation blocked as method is not allowlisted: <method>)
DVCS doesn’t work
There are log warns when entering any page (method needs allowlisting: com.atlassian.jira.projects.issuenavigator.DefaultIssueRenderService$FakeAction#getText(java.lang.String))
Missing translations on the Admin panel
After enabling a dark feature for an async webhook and restarting Jira, webhook payloads fail to send Parent Link data
In this release, we’ve removed the following feature flags:
com.atlassian.jira.agile.darkfeature.burnupchart
optimistic.transitions
com.atlassian.jira.advanced.audit.log
velocity.chart.ui
In this EAP release, we’ve removed yet another set of methods and classes that have been deprecated since Jira Software 9.x and Jira Service Management 5.x.
The More details section lists the methods and classes that we’ve already removed.
Here’s what’s already been removed:
Classes | Removed symbols | Instructions |
|---|---|---|
|
| Use |
|
| Use You now need to implement |
| All | Use |
| All | Use |
|
| Use |
|
| Use |
|
| Use |
|
| Use standard Java |
Rate this page: