Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

This page describes the supported platforms for JIRA 4.4.x. If a particular platform's version is not mentioned on this page, then we do not support that version of the platform for JIRA 4.4.x.

(info) Please also ensure you have read the JIRA Requirements page, since not all the platforms listed below may be required for your specific JIRA setup.

End of Support Announcements


Please read End of Support Announcements for JIRA for important information regarding the end of support for various platforms and browsers when used with JIRA.

Key: (tick) = Supported; (error) = Not Supported

Java Platforms


Oracle JDK / JRE (formerly Sun JDK / JRE)

(tick) 1.6 (update 18 or higher is required; update 24 or higher is recommended)
(error) 1.7

Operating Systems


Microsoft Windows (1)


Linux / Solaris (1, 2, 3)


Application Servers


Apache Tomcat (4)

(tick) 6.0.32 (bundled with JIRA Standalone)
(error) 6.0.0 – 6.0.19
(tick) 5.5.27, 5.5.28, 5.5.29




(tick) 5.x with JDBC Connector/J 5.1


(tick) PostgreSQL 8.2, 8.3, 8.4 with PostgreSQL Driver 8.4.x

Microsoft SQL Server

(tick) 2008 with the JTDS 1.2.4 driver
(tick) 2005 with the JTDS 1.2.4 driver
(error) Express Editions are not supported


(tick) 11G with Oracle 11.2.x drivers
(tick) 10G with Oracle 11.2.x drivers


(tick) (bundled with JIRA Standalone; supported for evaluation use only)

Web Browsers (6)


Microsoft Internet Explorer (7)

(tick) 7.0, 8.0, 9.0 ('Compatibility View' is not supported)

Mozilla Firefox (7)

(tick) Latest stable version supported
(tick) Tested with 3.6 (8), 4.0, 5.0, 6.0

Safari (7)

(tick) Latest stable version supported
(tick) Tested with 5


(tick) Latest stable version supported
(tick) Tested with 12


  1. JIRA is a pure Java-based application and should run on any supported operating system, provided that the JDK / JRE requirements are satisfied.
  2. Atlassian only officially supports JIRA running on x86 hardware and 64-bit derivatives of x86 hardware. If you are installing JIRA from an archive, you should create a dedicated user account on the operating system to run JIRA, since JIRA runs as the user it is invoked under and therefore can potentially be abused.
  3. Although the JIRA Linux Installer is designed to install successfully on all 'flavours' of Linux, we only test the JIRA Linux Installer on CentOS Linux. If you encounter problems with the JIRA Linux Installer on your particular flavour of Linux, we recommend installing JIRA on Linux from an archive file.
  4. Deploying multiple Atlassian applications in a single Tomcat container is not supported. We do not test this configuration and upgrading any of the applications (even for point releases) is likely to break it. There are also a number of known issues with this configuration (see this FAQ for more information).

    There are also a number of practical reasons why we do not support deploying multiple Atlassian applications in a single Tomcat container. Firstly, you must shut down Tomcat to upgrade any application and secondly, if one application crashes, the other applications running in that Tomcat container will be inaccessible.

    Finally, we recommend not deploying any other applications in the same Tomcat container that runs JIRA, especially if these other applications have large memory requirements or require additional libraries in Tomcat's lib subdirectory.

  5. JIRA ships with a built-in database (HyperSQL DataBase or HSQLDB). While this database is suitable for evaluation purposes, it is susceptible to data loss during system crashes. Hence, for production environments we strongly recommend that you configure JIRA to use an external database.
  6. Please refer to our Patch Policy on fixing browser issues.
  7. Minimum screen resolution of 1024 x 768 (when these browsers are maximised).
  8. Firefox version 3.6.0 possesses a bug that could result in data loss when used with JIRA. If you use this version of Firefox, please either upgrade your version of Firefox to 3.6.2 or above (preferably 5.0), or refer to our Firefox 3.6.0 caveats document for more details about this issue and how to avoid it.
  • No labels