We are excited to share our plans for our upcoming Jira 9.0 platform release for Server and Data Center. As a reminder, a platform release often includes multiple breaking changes that lay down the foundation for continued improvement in future 9.X feature releases. Jira 9.0 is focused on responsible scale, providing enterprise customers with the assurance that they can scale strategically, securely, and without performance impacts.
Please note that as the development of the release is underway, the specifics of breaking changes will evolve. This is our best estimate of areas with breaking changes at this point in time. Our early access program releases (EAP) will contain the full scope of breaking changes in Jira for 9.0, along with supporting documentation with more details and specifics.
We are targeting a number of improvements to end-user performance. There will be enhancements made within Issue-View focused on attachments, workflow transitions and activity tabs. Additionally, there will be improvements made through deferred scripts within Issue-View and potentially Backlog-View as well as the Dashboard page.
There are a number of platform and security upgrades planned for Jira, including XSRF protection improvements, Java API deprecations removals, security Jira WebActions and restricting anonymous access to REST endpoints.
We have been working on improving SLA consistency, scalability, and reliability with improvements to the way SLAs are calculated. As a part of this, we have introduced an improved default processor that’s more resilient and cluster-efficient. We have also changed the way events are processed in Jira Service Management (JSM), which will decrease the pressure on the event processing on instances with mixed Jira Service Management/Jira Software/Jira Core projects, speeding up the processing of SLAs, automation, and notifications. We will also be introducing a new interface to help administrators manage the way SLAs behave in an instance.
Bringing automation capabilities to the product will allow users to easily extend Jira to solve many of these use cases without the need to write code. Automation for Jira will automatically be included in Jira Software Data Center (Jira + JSM) from Jira 9.0 and beyond.
Early Access Program releases are designed to provide vendors visibility and an opportunity to develop against the changes of the upcoming platform release. Between now, and the Jira 9.0 release, we plan to have multiple EAP releases (including an EAP Beta, and finally the EAP Release Candidate) containing breaking changes, bug fixes and improvements. We plan to release the first EAP in-mid January 2022.
With the introduction of the first EAP for Jira 9.0, we will also create a community discussion topic under the Jira Server category specifically to address the changes introduced with 9.0, and will have members of the Jira Product Management and Engineering team on hand to help answer any questions. We’ll communicate ahead of the next EAP release and do our best to include most of the planned breaking changes as early as possible, to give you enough time to schedule changes to your app before the official Jira 9.0 release.
We know that a platform release can provide many unknowns. Here are some questions that we wanted to address with the information we currently have.
When will Jira 9.0 arrive?
As mentioned above, we cannot provide an exact date, but our current target to release Jira 9.0 is mid Q2 2022.
Will there be breaking changes to Jira’s APIs?
Yes, and we are still working on the full scope of breaking changes to either the REST API or Java API.
Are there any restrictions on who has access to the EAP builds of Jira 9.0?
No, there will not be any restrictions. The EAP is open to everyone.
Will there be additional resources to help us prepare?
Yes! In coordination with the EAP programs, we will provide more detail about breaking changes and the technical scope of Jira 9.0. We will also have technical documentation to provide detail on how to adopt the changes to Jira. We’ll be publishing all the documentation on the EAP page.
The Jira team