Cloud
Data Center 10.6
Versions

Preparing for Jira 10.6

Jira development releases

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

This documentation is intended for Jira developers who want to ensure that their existing apps are compatible with Jira Software Data Center 10.6 and Jira Service Management Data Center 10.6.

Latest version

Here you can find information about the latest EAPs.

Application

Date

Number

Version (Maven)

Downloads

Jira Software


 

 10.6.0-EAP02

10.6.0-m0003

Source files

Jira Service Management


 

 10.6.0-EAP02

10.6.0-m0003

Source files

Summary of changes

This section provides an overview of the changes we intend to make so that you can start thinking about their impact on your apps. Once the updates are ready, we'll indicate when they’ve been implemented and in which milestone.

Jira Software and Jira Service Management common features implemented in this EAP:

Jira Software and Jira Service Management common features

Status: IMPLEMENTED (EAP 01)

We're introducing a new REST API endpoint that makes it easier to create reciprocal issue links between different Jira instances. Previously, you needed to send two separate REST requests to achieve this. Now, with the following endpoint, you can establish these links with a single request.

(POST) {source_jira_url}/rest/api/2/issue/remotelink/reciprocal

This endpoint accepts a JSON payload specifying the source and target Jira instances, along with the necessary details for the link. To see the data format of this API endpoint, expand the content below.

Check the data format of the new API endpoint 
{
    "source": {
        "application": {
            "type": "com.atlassian.jira",
            "name": "{name_of_target_jira_instance}"
        },
        "globalId": "appId={id_of_application_link_to_target_instance}&issueId={id_of_target_issue}"
        "relationship": "{relationship}",
        "object": {
            "url": "{url_of_target_issue}", // url doesn't have to point to target issue
            "title": "{title_of_target_issue}", // title doesn't have to be target issue's title
            "summary": "{summary_of_target_issue}", // summary doesn't have to be target issue's summary
            "icon": { // icon isn't a mandatory field
                "url16x16": "{url_of_target_issue_type_icon}",
                "title": "{title_of_target_issue_type_icon}" // title doesn't have to be target issue type's title
            },
            "status": { // status isn't a mandatory field
                "resolved": "{true/false}",
                "icon": { // icon isn't a mandatory field
                    "url16x16": "{url_of_target_status_icon}",
                    "title": "{title_of_target_status_icon}"
                }
            }
        }
    },
    "target": {
        "application": {
            "type": "com.atlassian.jira",
            "name": "{name_of_source_jira_instance}"
        },
        "globalId": "appId={id_of_application_link_to_source_instance}&issueId={id_of_source_issue}"
        "relationship": "{relationship}",
        "object": {
            "url": "{url_of_source_issue}", // url doesn't have to point to source issue
            "title": "{title_of_source_issue}", // title doesn't have to be source issue's title
            "summary": "{summary_of_source_issue}", // summary doesn't have to be source issue's summary
            "icon": { // icon isn't a mandatory field
                "url16x16": "{url_of_source_issue_type_icon}",
                "title": "{title_of_source_issue_type_icon}" // title doesn't have to be source issue type's title
            },
            "status": { // status isn't a mandatory field
                "resolved": "{true/false}",
                "icon": { // icon isn't a mandatory field
                    "url16x16": "{url_of_source_status_icon}",
                    "title": "{title_of_source_status_icon}"
                }
            }
        }
    }
}


Remove deleted users marked as inactive

Status: IMPLEMENTED (EAP 01)

If users are deleted externally, they remain marked as inactive in Jira. You can now remove these users directly from the User management view. Learn how to remove a user

This feature is on by default. To turn it off, disable the com.atlassian.jira.user.allowDeleteExternallyDeletedUsers feature flag.

Status: IMPLEMENTED (EAP 02)

We've added a new database integrity check to ensure that all issue links in Jira are associated with valid issue link types.

This change addresses a common problem when issue link types are deleted from the database but remain in the user interface, causing errors during reindexing. The new integrity check detects and deletes such links from the database, ensuring an uninterrupted reindexing process.

Learn more about database integrity checks

New supported database versions

Status: IMPLEMENTED (EAP 02)

We’ve added support for new database versions:

  • Java 21 - runtime level
  • PostgreSQL 16
  • MySQL 8.4
  • Oracle 23ai

End-of-support announcements

Status: IMPLEMENTED (EAP 02)

In Jira 10.6, we’ve deprecated:

  • PostgreSQL 15
  • JDK 17
  • MySQL 8.0
  • MSSQL Server 2017

In Jira 11, we’ll remove support for:

  • JDK 17
  • PostgreSQL 15
  • PostgreSQL 14
  • PostgreSQL 13
  • PostgreSQL 12
  • MySQL 8.0
  • Oracle 18c
  • MSSQL Server 2017
Last modified on Apr 22, 2025

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.