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 8.16. If you're looking for a different version, select it at the top-right.


(tick) Supported - you can use Jira 8.16 with this platform.

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

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

Further information:


Oracle JRE / JDK:

(tick) Java 8

(tick) Java 11


(tick) Java 8

(tick) Java 11

Good to know:

Oracle JRE / JDK

  •  Jira will not work on:
    • Oracle Database Express Editions
  • We recommend using the Critical Patch Update (CPU) releases.

OpenJDK / AdoptOpenJDK

  • Our Support and Engineering teams use AdoptOpenJDK to replicate any issues raised with OpenJDK. If you’re using a different distribution of OpenJDK (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 AdoptOpenJDK JRE is bundled with Jira.

Operating systems

Operating systems:

(tick) Microsoft Windows

(tick) Linux 

(info) Mac OS X

(tick) Amazon Web Services ()

(tick) Microsoft Azure

Good to know:

  • 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:


  • We perform tests on Ubuntu.


  • If you’re creating your own deployment in 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


Desktop browsers:

(tick) Chrome (latest stable version)

(tick) Microsoft Edge Legacy (latest stable version)

(tick) Mozilla Firefox (latest stable version) 

(tick) Safari on Mac OS X only (latest stable version)

Mobile browsers:

(tick) Chrome (latest stable version)

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

(tick) Android 4.0 (Ice Cream Sandwich) 

Good to know:

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


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



(tick) PostgreSQL 11

(tick) PostgreSQL 10

(warning) PostgreSQL 9.6 (will be removed in Jira 8.19)

Jira is tested and bundled with the 42.2.6 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.


(tick) MySQL 8.0

(tick) MySQL 5.7 

Jira 8.x

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


(tick) Oracle 19c

(tick) Oracle 18c

(tick) Oracle 12c R2

    • 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 2017

(tick) SQL Server 2016

    • Jira will not work on:
      • Express Editions of Microsoft SQL Server
    • Supported Microsoft SQL databases use the Microsoft JDBC 7.2.1 Driver.

Microsoft Azure

(tick) Azure SQL / Azure SQL Database Managed Instance

(tick) Azure Database for PostgreSQL

Amazon Aurora (Data Center only)

(tick) PostgreSQL 11

(tick) PostgreSQL 9.6

  • 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 (evaluation only)

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

Environment and Infrastructure


  • You can use official templates to deploy Jira in a Docker container, or customize a Docker deployment on your own.
  • We support the Jira templates and can help with Jira-related problems, but we don't provide support for Docker itself.


  • NFS mounts are supported only for Jira Data Center's shared home directory. They won't work for Server, or DC's local home directory due to Lucene requirements. Read the IndexWriter docs for more information. 
  • 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.


  • 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 8.5.60. 
  • 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 Sep 1, 2023

Was this helpful?

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