Supported platforms

Before installing Jira, make sure you have the right software and infrastructure to run it. If a platform and version is not listed on this page, it means we don't test it, fix bugs or provide assistance for it. All platforms are shared between Jira Server and Jira Data Center, unless they're clearly marked as Data Center only.

This page is for Jira 9.5 . If you're looking for a different version, select it at the top-right.


Definitions:

(tick) Supported – you can use  Jira 9.5  with this platform.

(info) Limited – you can evaluate  Jira 9.5  on this platform, but you can't run a production site on it. 

(warning) Deprecated – you can use  Jira 9.5 with this platform, but we're planning to end support in an upcoming release.

Further information:

Java

JavaGood to know

Oracle JRE/JDK:

(tick) Java 8

(tick) Java 11

(tick) Java 17

Eclipse Temurin:

(tick) Java 8

(tick) Java 11

(tick) Java 17

Java

Eclipse Temurin/Eclipse Adoptium

  • Our Support and Engineering teams use Eclipse Adoptium to replicate any issues raised with Eclipse Temurin. If you’re using a different distribution of Eclipse Temurin (e.g. Zulu), we’ll still provide support for our products. However, if the bug is caused by a problem in Java distribution, we’ll ask you to reach out to the Java distributor for help.
  • You don't need to install Java if using the Windows Installer or Linux Installer as Eclipse Adoptium JRE is bundled with Jira.

To see the compatibility between your Jira version and the version of Eclipse Adoptium (AdoptOpenJDK), check Bundled Tomcat and Java versions. In the tables, see Tested JREs.

Operating systems

Operating systemsGood to know

(tick) Microsoft Windows

(tick) Linux 

(info) macOS

(tick) Amazon Web Services ()

(tick) Microsoft Azure

Jira is a pure Java-based application and should run on any supported operating system, provided that the JDK / JRE requirements are satisfied.

Microsoft Windows:

Read Anti-Virus in Jira applications. 

Linux:

We perform tests on Ubuntu.

Azure:

  • If you’re creating your own deployment in or Azure, you can use any configuration (e.g. OS or database) that’s supported both by Jira and Azure.

The Azure Resource Manager template as a method of deployment is no longer supported or maintained by Atlassian. You can still customize it for your own usage to deploy Data Center products on Azure though.

We recommend deploying your Data Center products on a Kubernetes cluster using our Helm charts for a more efficient and robust infrastructure and operational setup. Learn more about deploying on Kubernetes

Browsers

BrowsersGood to know

Desktop browsers:

(tick) Chrome (latest stable version)

(tick) Microsoft Edge (Chromium, latest stable version)

(tick) Mozilla Firefox (latest stable version) 

(tick) Safari on macOS only (latest stable version)

Mobile browsers:

(tick) Chrome (latest stable version)

(tick) Safari on iOS only (latest stable version)

We support a minimum screen resolution of 1024 x 768 (when browsers are maximized).

Mobile:

You can view Jira on a mobile device using the Jira mobile app or the mobile view (browser).

Databases 

PostgreSQL:

(tick)  PostgreSQL 14

(tick)  PostgreSQL 13

(tick)  PostgreSQL 12

(tick)  PostgreSQL 11

(tick)  PostgreSQL 10

Jira is tested and bundled with the 42.2.25 JDBC driver. You can also use the latest JDBC driver for your PostgreSQL version, though we can't guarantee it will work with your version of Jira. To use a different JDBC driver:

  1. Stop your Jira instance.
  2. Remove the bundled driver from <JIRA_INST>/lib/.
  3. Download the new driver and place it in <JIRA_INST>/lib/.
  4. Restart your Jira instance.

Jira 8.x

Jira does not support reducing the blocksize parameter below its default value.

MySQL:

(tick) MySQL 8.0


  • Jira will not work on:
    • MariaDB nor PerconaDB
  • We recommend running MySQL in strict mode.
  • Supported driver:

Jira 8.x

Jira does not support reducing the innodb_page_size parameter below its default value.

Oracle

(tick) Oracle 19c

(tick) Oracle 18c

(tick) Oracle 12c R2


  • Jira will not work on Oracle Database Express Editions. We recommend using the Critical Patch Update (CPU) releases.
  • Jira will not work on Oracle Advanced Compression Option (ACO).
  • JDBC Driver: For all Oracle versions, use the JDBC 19.3 (ojdbc8) driver listed here. This is the driver we’re using to test Jira with Oracle.

Jira 8.x

Jira does not support reducing the DB_BLOCK_SIZE parameter below its default value.

Microsoft SQL Server

(tick) SQL Server 2019

(tick) SQL Server 2017

(tick) SQL Server 2016


Jira is tested and bundled with version 9.2.1.jre8 of the Microsoft JDBC driver. You can also use the latest JDBC driver for your version of Microsoft SQL Server, though we can't guarantee it will work with your version of Jira. To use a different JDBC driver:

  1. Stop your Jira instance.
  2. Remove the bundled driver from <JIRA_INST>/lib/.
  3. Download the new driver and place it in <JIRA_INST>/lib/.
  4. Restart your Jira instance.

Jira will not work on Express Editions of Microsoft SQL Server.

Jira 8.x

Jira does not support reducing the blocksize parameter below its default value.

Microsoft Azure

(tick) Azure SQL

(tick) Azure PostgreSQL Flexible Server - one primary node only

(info) Azure Database for PostgreSQL - Single Server

We're aware that the Azure Database for PostgreSQL - Single Server is scheduled for retirement in 2025.

Amazon Aurora (Data Center only)

(tick) PostgreSQL 14

(tick) PostgreSQL 13

(tick) PostgreSQL 12

(tick) PostgreSQL 11

(tick) PostgreSQL 10

  • The only supported Amazon Aurora config is a PostgreSQL-compatible clustered database with one writer replicating to zero or more readers. Learn more

Embedded database

(info) H2 2.1.214 (evaluation only)

    • Jira ships with a built-in database (H2).

To get an overview of all supported databases and their compatibility with Jira versions, check Jira databases compatibility matrix. The matrix complements this document and contains the latest information about added or removed support for a particular database.

Environment and Infrastructure

Containerization

You can use official images to deploy Jira in a Docker container or customize a Docker deployment on your own.

We support the Atlassian Docker templates and can help with Jira related problems. We don't provide support for Docker itself or problems with any Docker environment.

Containerization manager

We recommend that you use official helm charts to deploy Jira Data Center with Kubernetes or customize a Kubernetes deployment on your own with the reference to the official helm charts.

We support the Atlassian Kubernetes helm chart and can help with Jira Data Center product-related problems. We don't provide support for Kubernetes itself or problems with any Kubernetes environment.

Read our Kubernetes support disclaimer and more about what we support and what we don’t.

Hardware

  • NFS mounts are supported only for Jira Data Center shared home directory. Due to Lucene’s requirements, NFS mounts won't work for Server or Data Center local home directory. Read the IndexWriter docs for more information. 
    •  The following NFS versions are supported: 4.0 and 4.1. We use them during Jira tests.
  • We only support Jira running on x86 hardware and 64-bit derivatives of x86 hardware.
  • If you are installing Jira from an archive, create a dedicated user account on the operating system to run Jira, since Jira runs as the user it is invoked under, it can potentially be abused.

Virtualization

  • VMware supports all of the operating systems listed under 'Operating systems'.
  • We don't provide support for VMWare itself.
  • Read Virtualizing Jira for information on how to configure VMWare.

Application server

  • We support Apache Tomcat 9.0.56. 
  • We don't support deploying multiple Atlassian applications in a single Tomcat container. 

Internet protocols (IP)

  • We support IPv4.
  • We support IPv6 with some limitations. See IPv6 in Jira.

External user directories

You can manage users in the following directories:

  • Apache Directory Server 1.0.x
  • Apache Directory Server 1.5.x
  • Apple Open Directory (Read-Only)
  • FedoraDS (Read-Only Posix Schema)
  • Generic Directory Server
  • Generic Posix/RFC2307 Directory (Read-Only)
  • Microsoft Active Directory
  • Novell eDirectory Server
  • OpenDS
  • Open
  • Open (Read-Only Posix Schema)
  • Sun Directory Server Enterprise Edition

Mail servers

  • SMTP servers must be able to support the multipart content type.

Last modified on Oct 3, 2024

Was this helpful?

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