Preparing for Jira 9.10

This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira 9.10.

Upgrading from 8.x to 9.x triggers full Jira reindex that causes some downtime during the process. If you’re on 8.x now, make sure you’ve estimated the downtime and set the best time for the upgrade.

Learn more about how to handle full reindex and estimate downtime

Quick info

Latest version

Here you can find information about the latest EAPs.

Application/Date numberVersion (Maven)Downloads

Jira Core/Software

 

9.10.0-RC01

9.10.0-m0003


Source files (Core)

Source files (Software)

Jira Service Management

 

5.10.0-RC01

5.10.0-m0003

Source files

Summary of changes

In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your apps. Once they're ready, we'll indicate when a change has been implemented, and in which milestone.

Accessibility improvements for low-vision and keyboard-only users DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE

We’re bringing more accessibility updates for screen reader and keyboard-only users. The highlights for this release include an improved label description in the Kanban board and fixed navigation when creating an issue.

Check out the full list of fixed issues

Get a message about Jira reindex only when it’s really required DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE JIRA SERVICE MANAGEMENT

A message about the required Jira reindex will no longer pop up after you simply restart Jira. The message will appear only after you make major configuration changes in your instance. For example, after you add a custom field or change the time tracking settings.

Learn more about Jira re-index after different instance configurations

We made some investigation to find out why the message about the required reindex appeared after the Jira restart. We discovered that after the restart, the plugins using custom fields got enabled automatically. This issue triggered the message when the reindex wasn’t needed.

We’ve fixed this behavior to inform you about the reindex only when it’s really required and to strengthen your confidence in administrative operations in Jira.

Deprecating unused functions in UrlState.js DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE

As a part of cleaning the Jira codebase for better code efficiency, we’re deprecating the following functions in the UrlState.js library:

  • isUrlStateUpToDate()
  • historyChanged()
  • logDifferenceInState()
  • init()

These functions will be completely removed from the codebase in Jira 9.11. To ensure that your apps work correctly, update your apps' code to remove unused functions.

Obfuscating the plain text password in server.xml for Tomcat DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE

As a Jira administrator, you can now obfuscate the plain text password used in the server.xml file for Tomcat by using Jira’s out-of-the-box password cipher method – basic encryption with Base64Cipher. Using the plain text password as is might be unsafe and introduce vulnerabilities to the system.

Create and edit linked issues with usual issue screens DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE JIRA SERVICE MANAGEMENT

We’re introducing a new Create linked issue screen, an out-of-the-box solution for creating linked issues between Jira Software projects or between Jira Software and Jira Service Management projects. This eliminates the need for complex workarounds with screen and field configurations.

For example, before the update, when you wanted to add a field to a linked issue, you’d need to add this field to the Create issue screen of the original issue in a current project. Then, in the field configuration, you’d need to set the field as required. Only after these steps, the desired field would appear on the Create linked issue screen.

We’ve considered your feedback about this time-consuming and inconvenient process, and now creating and working with linked issues has finally become more comprehensive and user-friendly. You can configure fields in the linked issue directly, on the Create linked issue screen.

Under the More menu on an issue, you’ll find the Create linked issue option. Select it to open a linked issue screen with default and custom fields prepopulated with the latest values you’ve used when working on other issues. For example, if the last issue type you selected was a story, it’ll be preset in the Issue Type field of the new linked issue.

The fields in the linked issue automatically reflect the fields of a destination project. You can edit them on the Create linked issue screen as needed.

Create a linked issue

Identify request types by groups DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SERVICE MANAGEMENT

Say goodbye to requests ending up in the wrong queues. Groups names associated with request types will now be visible in the search results and the recent requests sections of the portal and the global help center. This additional context will allow help seekers to distinguish between request types with similar names and help them select the appropriate request type, reducing service inefficiencies. and providing quality support. 

Request type group names (1 in the screenshots) will be now be visible in the following locations:

  • The search results of the help center.
    Group name displayed within search results of the help center
  • The search results of the portal associated with a particular project.
    Group name displayed within the search results of the portal
  • The recent requests section of the help center.
    Group name displayed within the recent requests section of the help center

What do you need to know?

The group names are listed based on their order in project settings. To change the order, modify the group order from Project settings > Request types. Learn how to set up request types

Translation support is available for request type groups, and the translated text will be displayed on both the portal and the help center. However, if your help center uses the same group name in multiple projects, you’ll need to add translations in each project to make sure that the group name is translated.

New field in dashboard gadgets 

Status: IMPLEMENTED (eap01)

App: JIRA SERVICE MANAGEMENT

We’re adding the Customer Request Type field to dashboard gadgets. Project admins and agents will be able to include this field in gadgets and generate reports based on request types. As this custom field is exclusive to Jira Service Management projects, it isn’t available in gadgets of other Jira project types.

Learn how to configure dashboards

Customer request type field within pie chart gadget

  1. Customer request type field within the Pie Chart gadget.

Clone queues to save time DATA CENTER

Status: IMPLEMENTED (eap01)

App: JIRA SERVICE MANAGEMENT

We’re introducing the ability to clone queues within the same project. Project admins no longer need to create new queues from scratch. They can conveniently clone queues within the same project and customize these queues to meet specific needs. Issue filters (including JQL for advanced filters) and column settings are copied to the cloned queue.

To clone a queue in your service project, navigate to Queues, select the queue you wish to clone, and then select More actions () > Clone queue

Learn how to set up queues for your team

Clone queue from the more actions menu

  1. Clone queue option within the More actions menu.

Search for projects and issue types in custom field contexts

Status: IMPLEMENTED (eap02)

App: JIRA SOFTWARE JIRA SERVICE MANAGEMENT

The UI for this feature is still a work in progress and to offer the best possible user experience, it is not currently available by default. To access the new functionality, turn on the jira.customfields.configure.modern.ui feature flag.

Learn how to enable dark features in Jira

On large instances with custom fields reused across numerous projects, finding the needed contexts can take some time. Especially if you want to add or remove a issue type or project from the context, but don’t know exactly where they appear. To make this process more efficient, we’ve introduced the Projects and Issue types menus.

When you select a particular item in a menu, you’ll see the list of contexts it appears in. Keep in mind that the same project can’t appear in more than one context. Learn more about configuring contexts for custom fields

A custom field context that matches two projects selected in the Projects menu

Two custom field contexts that match issue types selected in the Issue types menu

The information in the Contexts table might vary depending on the field type.

Such columns as Context, Issue types, Projects, and Actions are always displayed for any custom field. However, if your field has specific customization or multiple properties, such information will be added as extra columns to the table.

Jira Mobile updates

Here are the new features we’re introducing in both Jira Software and Jira Service Management for Mobile.

Log in to your mobile applications without connection and compatibility errors

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE JIRA SERVICE MANAGEMENT

Platform: ANDROID IOS

Thanks to optional pre-login backend validation, you can easily log in to previously unavailable instances of Jira Software and Jira Service Management for Mobile. As a Jira administrator, you don’t need to configure any additional setup.

Before this fix, to allow the login, the mobile application had to check that you were running a compatible version of the main application – Jira Software or Jira Service Management. To do this, the mobile application tried to access <jira-base-url>/server-info> without any authentication. However, environments like Azure Application Proxy can’t be accessed without authentication. That’s why the mobile application notified you about a connection or compatibility issue.

Now, this application pre-login validation is optional, and the login procedure is unblocked for all mobile users.

Mobile users on iOS can add attachments through comments

Status: IMPLEMENTED (eap01)

App: JIRA SOFTWARE JIRA SERVICE MANAGEMENT

Platform: IOS

If you’re using Jira Software or Jira Service Management for Mobile on an iOS device, you can now attach files not only to the Description field in issues but also to issue comments.

Supported platforms DATA CENTER

In Jira 9.10, we’re adding support for:

  • PostgreSQL 15
  • SQL Server 2022
  • PGpool-II

Learn more about supported platforms

We’re keen to hear your feedback on the new capabilities released with Jira Software 9.10 and Jira Service Management 5.10. Would you like any additional features or improvements to them? Use the Provide feedback about this article link at the bottom of this page to share your thoughts with us.

Last modified on Jul 8, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.