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

Skip to end of metadata
Go to start of metadata

JIRA is a 'web application', meaning it runs centrally on a server, and users interact with it through web browsers from any computer.

(info) If you are considering running JIRA on VMware, please read the Running JIRA in a Virtualised Environment.

JIRA Client/Server Software Requirements

Please read the Supported Platforms page for JIRA, which lists the required server and client software supported by JIRA 4.3.x, including:

  • Browsers (client-side)
  • Java platforms (JDK/JRE) (server-side)
  • Operating systems (server-side)
  • Application servers (if you are installing JIRA WAR-EAR) (server-side)
  • Databases (server-side)

Please also read the information below regarding server and client software requirements for JIRA.

1. Browser

If you have disabled JavaScript in your browser or are using a script blocking tool like NoScript, you must enable your browser to execute JavaScript from JIRA to access JIRA's full functionality.

2. Java

JIRA requires a Java Developers Kit (JDK) or Java Runtime Environment (JRE) platform to be installed on your server's operating system. (Refer to Supported Platforms for supported Java Platforms). For instructions on how to do this, please refer to Installing Java.
(info) Currently, Oracle JDK/JRE (formerly Sun JDK/JRE) is available for Windows (32 bit + 64 bit), Solaris (32 bit + 64 bit) and Linux Platforms (32 bit + 64 bit).
     Mac OSX systems are packaged with a JDK optimised for their hardware and operating systems. However, these JDKs are not supported by JIRA.

3. Application Server

JIRA is a web application that requires an application server.

  • JIRA Standalone ships pre-configured with Apache Tomcat, which is a stable, lightweight and fast-performing application server. (There is no need to install a separate application server if you download the JIRA Standalone distribution.)
  • JIRA WAR/EAR can be installed into an application server (supported by Atlassian), provided this application server is compatible with your operating system and JDK. You must manually configure your JIRA WAR/EAR installation to operate with an existing application server installation.

4. Database

JIRA requires a relational database to store its issue data. JIRA supports most popular relational database servers, so we suggest using the one that you are most comfortable with administering.

  • JIRA Standalone ships pre-configured with the HSQLDB database, which is suitable for evaluation purposes only. HSQLDB is prone to database corruption. Before deploying JIRA to a production environment, we strongly recommend that you connect JIRA Standalone to an enterprise database (supported by Atlassian).
  • JIRA WAR/EAR can be connected to an enterprise database (supported by Atlassian).

JIRA Server Hardware Recommendations

During evaluation, JIRA will run well on any reasonably fast workstation computer (e.g. 1.5+ Ghz processor). Memory requirements depend on how many projects and issues you will store, but 256MB ( of Java heap size ) is enough for most evaluation purposes. (Note: most people start by installing JIRA Standalone on their local computer. It is easy to move JIRA to a production server later).

The hardware required to run JIRA in production depends mainly on the number of issues and users that your installation will have, as well as the maximum number of concurrent requests that the system will experience during peak hours.

  • If you are planning to have a small number of projects (10-20) with 1,000 to 5,000 issues in total and about 100-200 users, a recent server (2.0+GHz Quad Core CPU) with 1-2GB of available RAM should cater for your needs.
  • If you are planning for a greater number of issues and users, adding more memory will help. We have reports that allocating 1GB of RAM to JIRA is sufficient for 100,000 issues. If in doubt, allocate more memory than you think you need.
  • If your system will experience a large number of concurrent requests, running JIRA on a multi-CPU machine will increase the concurrency of processing the requests, and therefore speed up the response time.

For reference, jira.atlassian.com has over 70,000 issues and over 30,000 user accounts. The system runs on a 64bit Quad processor. The server has 32 GB of memory with 1.5 GB allocated to JIRA.

Please note that performance heavily depends on your usage pattern. As a general rule, if you wish to store more than 200,000 issues in JIRA we recommend that you set up separate instances of JIRA on different physical machines and split your projects and issues between the instances. You can follow the instructions on splitting a JIRA instance, if you need to convert an existing JIRA instance into multiple instances.

We would appreciate it if you let us know what hardware configuration works for you. Please create a ticket in our support system with your hardware specification and mention the number of users and issues in your JIRA installation.

Icon

JIRA requires access to a local disk for certain functionality (e.g. if JIRA does not have read and write access to disk, searching and attachments will not work).

Icon

While some of our customers run JIRA on SPARC-based hardware, Atlassian only officially supports JIRA running on x86 hardware and 64-bit derivatives of x86 hardware.

Next Steps