Preparing for Jira 9.9 | Atlassian Support (2023)

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

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



Source files(Core)

Source files(Software)

Jira Service Management



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.

Integrate Jira Software with Microsoft Graph APIDATA CENTER

Status:IMPLEMENTED (eap01)


Jira Software mail servers are getting a new feature — Microsoft Graph API integration for incoming mail. To use Microsoft Graph API, you need to configure an Azure Active Directory integration and then, create an incoming mail server and a mail handler in Jira Software. After you’re done with the configuration, your mailbox will be monitored and emails that you receive will be turned into issues or comments.

By using the Microsoft Graph API protocol, you ensure robust data security in your Jira instance, protecting it from unauthorized access, corruption, and breaches.

Learn more about how to set up a mail server with Microsoft Graph API

Learn more about creating issues and comments from email

Show empty custom fields in the issue view DATA CENTER

Status:IMPLEMENTED (eap01)


Working with custom fields becomes easier and more efficient as we introduce the Empty custom field configuration. Jira users no longer need to edit the issue or navigate to the issue details view each time they have to fill in an empty field — such fields can now be visible in the issue view.

How to make empty fields visible in the issue view

The feature can be configured on two levels:

  • On the instance level. Jira admins can turn on the Show when empty toggle from the Jira administation menu, on the Configure screen page.
  • On the project level. Jira admins and Project admins can turn on the Show when empty toggle in the Project settings, on the Issue types and Screens tabs.

Preparing for Jira 9.9 | Atlassian Support (1)

Configuration on the instance level

  1. Screens tab. Here Jira admins can view all screens that have been defined in Jira.

  2. Show when empty toggle. When enabled, empty fields will be visible in the issue view.

Preparing for Jira 9.9 | Atlassian Support (2)

Configuration on the project settings level

  1. View issue screen. Here Jira and Project admins can configure screens for different issue types.

  2. Show when empty toggle. When enabled, empty fields will be visible in the issue view.

Preparing for Jira 9.9 | Atlassian Support (3)

Configuration on the project settings level

  1. Screens tab. Here Jira and Project admins can modify screen schemes and configure screens for different issue operations.

  2. Show when empty toggle. When enabled, empty fields will be visible in the issue view.

Learn more about Jira screens and their configuration

Changes to the API

Extended the response of the following endpoints with a new boolean field showWhenEmpty:

  • api/2/screens/{screenId}/tabs/{tabId}/field for GET/POST requests
  • api/2/screens/{screenId}/availableFields for GET requests
Example of the old response
[ { "id":"customfield_10000", "name":"custom_field", "type":"Checkboxes" }]
Example of the new response
[ { "id":"customfield_10000", "name":"custom_field", "type":"Checkboxes", "showWhenEmpty":true }]

We’ve also introduced a new endpoint for PUT requests: api/2/screens/{screenId}/tabs/{tabId}/fieldsV2/{id}/updateShowWhenEmptyIndicator/{newValue} . This endpoint only returns the HTTP 204 status if the operation was successful.

Project role assignment in Jira Importer Plugin (JIM) DATA CENTER

Status:IMPLEMENTED (eap01)


The Jira Importer Plugin (JIM) no longer automatically creates and assigns the Developers project role to all project leads and assignees in the imported file by default. You need to turn it on with a parameter.

In the CSV import, you’ll find a checkbox for this mechanism and the new importSettings field in the config file config.create.and.assign.default.project.role. To switch it on, set this parameter to true. If this parameter is set to another value or isn't included at all, the mechanism won't be triggered. Learn more about importing data from JSON

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

Status:IMPLEMENTED (eap01)


We’re bringing more accessibility updates for screen reader and keyboard-only users. The highlights for this release include improved roles, attributes, labels, and navigation in Assets objects and search.

Check out the full list of fixed issues

Status:IMPLEMENTED (eap01)


Sharing requests with Jira groups will contribute to the scalability of the service desk and customer management in your instance. With this new feature, service desk admins can enable their internal customers (employees) to share requests with other members of the Jira groups they’re assigned to without additional permission management.

The feature brings several perks for all help seekers on the customer portal:

  • By using a dedicated toggle in the user interface, all internal customers can share requests with groups they are a part of, in addition to their organizations. This ability eliminates the risk of request duplication, thus reducing the load on support.

  • Admins can create automation rules to share requests with appropriate groups, while agents can share requests with groups to collect insights from a larger internal audience through a single form.

  • Project admins no longer have to rebuild internal customer groups within their organizations or manually add group members as request participants to grant them access to the requests. For example, if a project admin wants to enable voting through the customer portal, they can simply build a pool of potential internal voters for a request without seeking individual access for each person.

Run imports on dedicated nodes and track the progress of the operations DATA CENTER

Status:IMPLEMENTED (eap01)


We continue releasing a series of planned improvements around Assets import. In Jira Service Management 5.9, we’re rolling out the following updates to improve the admin experience:

  • You can run manual imports on the same nodes that you configure for scheduled imports. A request for a manual import operation will send a cluster message to the other nodes, so only a dedicated node will handle the import. Having a dedicated node for resource-consuming scheduled and manual imports allows you to control the overall performance of a pool without scaling up every single node.

  • The progression of imports and other operations will be shared across all nodes and will be visible in the Process results tab on any node.

Preparing for Jira 9.9 | Atlassian Support (4)

The progression of imports will also be shared across your database for the number of executed units of work that you can set in the Assets configuration. A unit of work quantifies the frequency of updates to the database for an operation in progress.

For example, in the case of a CSV import, a unit of work represents a single row in the CSV file where a row is an Assets object. For the interval of 100 units of work, the status of the import operation will be updated in the database every time 100 new objects are imported.

The default number of units of work is 100. To change this value:

  1. Go to Administration > Manage apps.
  2. In the left-side panel, select Assets configuration.
  3. Select Edit settings.
  4. In the Data Center section, edit the value of Frequency of updates for the status of an action in progress.
  5. Select Save.

Email notification performance speed-up DATA CENTER

Status:IMPLEMENTED (eap01)


With some backend magic, a Jira instance can now send 30,000 email notifications per minute. This is 9 times faster than the previous capacity of 4,000 emails per minute.

This performance boost aims at taking down the email delay on your instance from hours to minutes or even to zero, depending on how large an instance is.

Comments on approvals are now supported in Jira Service Management for Mobile

Status:IMPLEMENTED (eap01)


Using Jira Service Management on your mobile device? You can now leave comments when approving or declining requests there, just like in the web version of the application. Enjoy the seamless experience of managing requests on any device. Learn more about approvals in JSM

We’re keen to hear your feedback on the new capabilities released with Jira Software 9.9 and Jira Service Management 5.9. 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.

Top Articles
Latest Posts
Article information

Author: Madonna Wisozk

Last Updated: 23/05/2023

Views: 6452

Rating: 4.8 / 5 (48 voted)

Reviews: 87% of readers found this page helpful

Author information

Name: Madonna Wisozk

Birthday: 2001-02-23

Address: 656 Gerhold Summit, Sidneyberg, FL 78179-2512

Phone: +6742282696652

Job: Customer Banking Liaison

Hobby: Flower arranging, Yo-yoing, Tai chi, Rowing, Macrame, Urban exploration, Knife making

Introduction: My name is Madonna Wisozk, I am a attractive, healthy, thoughtful, faithful, open, vivacious, zany person who loves writing and wants to share my knowledge and understanding with you.