As we announced in December of last year, there are multiple security and usability updates for Data Center products coming your way in 2025.
What’s changing?
To maintain high security standards and improve accessibility and usability, we’re planning the following changes:
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
Note that we’re no longer including basic authentication disabled by default as part of these updates.
Where to track the updates?
Visit this page to learn more about the upcoming changes, find resources, useful dates, and links. Make sure to follow the changelog to keep track of the updates and check out product documentation for product-specific details.
When can you test the changes?
To allow you to test your apps ahead of time and make sure they’re compatible with the changes, we’ll be publishing multiple Early Access Program (EAP) releases over the coming months, whenever we have something new to share. This way, you can integrate the changes gradually. If you prefer to wait until the final EAP to test all the changes at once, we’ll also let you know when it’s ready.
Here are the estimated release dates for the first EAPs containing these changes:
Will we as Marketplace Partners have as much to do as we had with Jira 10 and JAX-RS v2 upgrade? Or will this simply be a drop in replacement of the dependency?
Thank you for your question! The short answer is no.
In REST v2, which we introduced in the previous major version, we focused on concealing implementation details. The new API primarily utilizes the Jakarta API, complemented by a few additions from our own API, mainly annotations.
We are currently migrating from Jakarta 8 to Jakarta 10. For the ws.rs-api, this means an upgrade from version 2.1 to 3.1. The only change introduced in version 3.0 (part of Jakarta 9) was a shift in the Java package namespace from javax.* to jakarta.*. Importantly, version 3.1 does not introduce any backward-incompatible changes.
Based on our expectations and experiences with migrating our own components, the only adjustments required will be in the Java import statements (for example, changing import javax.ws.rs.GET; to import jakarta.ws.rs.GET;).
Please keep in mind that while this change is straightforward, it does break binary compatibility and necessitates recompilation of the entire codebase. This is why we are planning to implement it in our upcoming major update.
Thanks for the update.
I noticed in the post that there was no mention of the previously announced plans introduce the “Jira search API” and stop exposing Lucene to Jira Apps as of Jira 11. Is this still planned to be part of Jira 11 release? Do we have any indication on whether that will be part of the EAP available in Q2 2025?
