Latest version

Here you can find information about the latest EAPs.

Summary of changes

In this section you will be provided with an overview of the changes that Atlassian intends to make in Jira 8.11, so you can start thinking how it might impact your apps. Once they’re ready, it will be indicated when a change has been implemented, and in which milestone.

Configure how fast stale nodes are moved offline DATA CENTER

Status: IMPLEMENTED (eap 01)

In Jira 8.10 Atlassian has made it possible for stale nodes to be automatically moved offline after two days of reporting no heartbeat. Now, you will be able to configure this timeframe and move stale nodes offline even after 3 hours by modifying the jira.not.alive.active.nodes.retention.period.in.hours system property.

Restricting sprint selection

Status: IMPLEMENTED (eap 01)

To help you add issues to the correct sprint when creating or editing an issue, the Atlassian team is enabling an admin option to restrict the sprint selection (available in the Sprint drop-down) only to the sprints belonging to the project users select. This way, they want to limit the possibility of linking issues to the wrong sprint.

Detail view optional

Status: IMPLEMENTED (eap 01)

Whenever a card is clicked on a board a new view is opened showing details about an issue. Now, Atlassian wants to make the Detail view opening an option you can save per board as your user preference. If you decide to keep the view closed, you’ll be able to select issues without the details pop-up opening.

To hide detail view, open your board and select Board > Hide detail view.

 

New events in the Advanced audit log DATA CENTER

Status: IMPLEMENTED (eap 01)

4 new events have been added to the Advanced audit log (General configuration and administration / Fields / Level: Advanced) that help you track issue statuses (Status deleted, Status created, Status order changed, Status updated).

 

Embedded Crowd upgrade

Status: IMPLEMENTED (eap 01)

Embedded Crowd is a library used in Jira for user management—all functions related to users and groups rely on it. The current version in Jira is 2.x, and we’re upgrading it to 4.0. Some of the benefits of this new version are:

• Performance improvements (improved sync times)
• Clustering support
• Improved directory failover
• A number of bugs fixed

This change might affect apps related to user management, so make sure to test your app with the EAP.

 

Managing private filters and dashboards

Status: IN PROGRESS (eap 01)

In Jira 8.11, Atlassian is giving Jira admins the power to edit and delete private filters and dashboards. Admins can view and search for all existing filters and dashboards from the administration area.

 

Setting max timeout for the Favorite Filters gadget

Status: IMPLEMENTED (eap 01)

A new global setting has been added that allows Jira admins to set the max timeout for the Favorite Filters gadget. This gadget is quite popular, and displays a list of filters and the number of issues each of them contains. For large filters, counting and showing the issues might affect Jira performance, so this setting is a fail-safe to make sure everything works right.

You can set it by going to Administration > System > General configuration. The default value is 5000 ms. If you set it to -1, Atlassian won’t count and show the issues at all.

 

Unbundling the Hipchat app

Status: IMPLEMENTED (eap 01)

As Hipchat reached its End of Life for Server and Data Center, Atlassian has unbundled the Jira integration for Hipchat app from Jira. If your plugins rely on some modules provided by this app, they will no longer be available.

 

MySQL 8 support

Status: MOVED TO 8.12

The Atlassian team is planning to support MySQL 8.

Apache Tomcat upgrade

Status: PLANNED

Apache Tomcat is upgraded from 8.5.50 to 8.5.56. This change will be available in EAP 2.

Providing help in multiple languages JIRA SERVICE DESK

Status: IMPLEMENTED (eap 01)

Jira Service Desk 4.11 will allow you to translate content in the customer portal and help center to provide help to your customers in their preferred language.

You’ll be able to translate your:

• request types (names, descriptions, fields, and groups)
• portal names
• announcements (login, help center, and portal)