JIRA is now available as three separate applications, JIRA Software, JIRA Service Desk, and JIRA Core. For more information on administering these applications, refer to the Administering JIRA Applications documentation.

JIRA Requirements

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 Virtualizing JIRA (JIRA on VMware).

No hardware? No problem! Try using JIRA Cloud.

  • No installation required, get started in 5 minutes
  • Option to migrate to your own server later
  • Choose from a set of supported add-ons to install

JIRA Client/Server Software Requirements

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

  • Browsers (client-side)
  • Java platforms (JDK/JRE) (server-side)
  • Operating systems (server-side)
  • Application servers (if you are installing the JIRA WAR distribution) (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.

If you intend to use the Windows Installer or Linux Installer to install JIRA, there is no need to install and configure a separate JDK/JRE since these executable files will install and configure their own JRE to run JIRA.

If, however, you intend to install JIRA from an archive or you plan to install the JIRA WAR distribution, then you will first need to install a supported Java platform. (Refer to Supported Platforms for supported Java Platforms). For instructions on how to install a supported Java platform for JIRA, please refer to Installing Java.

(info) Please Note:

  • Currently, Oracle JDK/JRE (formerly Sun JDK/JRE) is available for Windows (32-bit + 64-bit), Linux (32-bit + 64-bit) and Solaris Platforms (32-bit + 64-bit).
    Mac OS X systems are packaged with a JDK optimised for their hardware and operating systems. However, neither the Mac OS nor these JDKs are not supported by JIRA.
  • A JIRA installation running on a 64-bit Java platform may require additional memory (to run at a similar level of performance) to a JIRA installation running on a 32-bit Java platform.
    This is because a 64-bit Java platform's object references are twice the size as those for a 32-bit Java platform.

3. Application Server

JIRA is a web application that requires an application server. However, this requirement differs based on the type of JIRA distribution you intend to install:

  • 'Recommended' JIRA distributions (installed using 'Windows Installer', 'Linux Installer' or from an 'Archive File') are 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 intend to install one of these recommended JIRA distributions.)
  • The JIRA WAR distribution can be installed into an application server (supported by Atlassian), provided this application server is compatible with your operating system and Java platform. You must manually configure your JIRA WAR 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 ships pre-configured with the HSQLDB database, which is suitable for evaluation purposes only, since HSQLDB is prone to database corruption.

Hence, if you intend to use JIRA in a production environment, we strongly recommend that you connect JIRA to an enterprise database (supported by Atlassian).

5. Notes

  • Virus checking software are a common cause of performance problems. In particular, Symantec must be uninstalled from the server that you want to install JIRA on, as it is known to dramatically reduces JIRA performance (even stopping the services does not prevent it from slowing JIRA down).
    For more information, see this knowledge base article: Crashes and Performance Issues Troubleshooting

JIRA Server Hardware Recommendations

JIRA typically will not perform well in a tightly constrained, shared environment - examples include an AWS micro.t1 instance. Please be careful to ensure that your choice of hosting platform is capable of supplying sustained processing and memory capacity for the server.

JIRA Server Hardware Recommendation for Evaluation

During evaluation, JIRA will run well on any reasonably fast workstation computer (eg. something purchased within the last two years). Memory requirements depend on how many projects and issues you will store, but 300MB – 1GB (of Java heap size) is enough for most evaluation purposes.

(tick) There are two ways to evaluate JIRA:

  1. Start immediately with JIRA Cloud and then migrate to a local production server later, or simply continue to use JIRA Cloud.
  2. Install JIRA Server on a local computer and then migrate this to a production server later.

JIRA Server Hardware Recommendation for Production

The JIRA Sizing Guide could help you choose a server with sufficient resources based on your use case and usage.

The hardware required to run JIRA in production depends on a number of different JIRA configurations (eg. projects, issues, custom fields, permissions, etc) as well as the maximum number of concurrent requests that the system will experience during peak hours. Here are some general guide lines:

  • For a small number of projects (10-20) with 1,000 to 5,000 issues in total and about 100-200 users, a recent server (multicore CPU) with 2 GB of available RAM and a reasonably fast hard drive (7200rpm or faster) should cater for your needs.
  • For a greater number of issues adding more memory will help. We have reports that having 2GB of RAM to JIRA is sufficient for instances with around 200,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 multicore CPU machine will increase the concurrency of processing the requests and therefore speed up the response time for your users.
  • For reference we have a server that has a 2 Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (16 logical cores) with 32GB of RAM. This server runs Apache, various monitoring systems, and two JIRA instances:
    • Our public JIRA site that has approximately: 145,000 issues, 255,000 comments, 120 custom fields, and 115 projects. 
    • Our support JIRA site that has approximately: 285,000 issues, 2,500,000 comments, 75 custom fields, and 22 projects.

Please note that performance heavily depends on your dimensions and your usage pattern, much more than what is simply covered here. Therefore we have written a guide on the different methods you can use to scale JIRA in your environment

A quick note that your JIRA database's size is predominantly dominated by these three large tables: change items, comments and issues stored in your JIRA instance. Also, the type of custom fields and the values they hold may also increase the size of your JIRA database, eg. a free text custom field that is on every issue with grow the database size if the value of that field is large.

(warning) Please Note: JIRA requires access to a local disk for certain functionality. If JIRA does not have read and write access to a local disk, searching and saving/accessing attachments will not work.

(info) 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

Install JIRA.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

38 Archived comments

  1. User avatar


    Atlassian, are you planning on addressing the scalability of Jira?  As an administrator of a Jira instance with around 100k issues, I am very concerned about the possibility of splitting a Jira instance in the future.  I don't think it is a good solution and would hope that work is being done to address this issue. 

    02 Sep 2011
    1. User avatar

      Nancy Belser

      Thought I was logged in - the previous comment was from me.

      02 Sep 2011
    1. User avatar


      Agree with this. Need something done in this regard.

      03 Jul 2013
  2. User avatar


    I see you do not support Jira on Mac.  We run an all-mac shop.  Any plans of supporting Jira on macs in the future? 

    07 Sep 2011
    1. User avatar


      08 Sep 2011
      1. User avatar

        Christina Swearengin [Atlassian]

        We've removed that video.

        Mac OS X is not a supported operating system for the JIRA server because Oracle JDK and JRE (formerly Sun JDK and JRE), which are the only supported Java platforms for JIRA, are not available for this operating system. Mac OS X is packaged with a JDK optimised for its hardware. More details here:


        05 Oct 2011
        1. User avatar


          Now that Oracle does have a version of the JDK available for OS X, will Atlassian support deployments on OS X?

          14 Apr 2013
          1. User avatar

            Matt Doar (ServiceRocket)

            It's a funny thing. We all know that JIRA works on OSX because that's what it is mostly developed on. But since almost no-one uses OSX servers for their company there is not much to be gained (in my opinion) spending the testing time that would be needed for it. I run JIRA every day on OSX with no platform-related issues.

            15 Apr 2013
          1. User avatar

            Andrew Lui [Atlassian Technical Writer]

            Hi Werner,

            I have checked with our product managers and can confirm that Atlassian does not plan on supporting deployments on OS X. As Matt as suggested in his comment above, JIRA may run on an OS X server, however we do not test against it and do not fix bugs related to it.

            Kind Regards,

            16 Apr 2013
  3. User avatar


    What support and implications are there when running it in a VM environment?

    05 Oct 2011
      1. User avatar

        Sorin Sbarnea

        Very interesting to observe that the access to this page was restricted!?

        15 May 2013
        1. User avatar

          Matt Doar (ServiceRocket)

          That sounds like a bug because it didn't used to be.

          15 May 2013
        1. User avatar

          Andrew Lui [Atlassian Technical Writer]

          Hi Sorin,

          The page that Christina referred to has been deprecated in favour of this one: Virtualizing JIRA (JIRA on VMware). I had a deprecation notice on the old page for a little while and recently restricted it. It will be deleted soon as it is out of date.

          Apologies for the confusion.

          Kind Regards,

          20 May 2013
          1. User avatar

            Brian Surratt


            The "new" page, Virtualizing JIRA (JIRA on VMware), does not resolve.  Is there a new page with this information?    

            Thank you

            10 Jul 2014
            1. User avatar

              Warren Thompson

              Hi Brian,

              Try here: Virtualizing JIRA (JIRA on VMware). We've just released JIRA Data Center and our docs have had a bit of a shake up. Apologies for the confusion.



              11 Jul 2014
              1. User avatar

                Brian Surratt

                Good stuff. Thank you.

                14 Jul 2014
              1. User avatar

                William Crighton [CCC]


                The invalid link also appears on this page - could you guys update it on this page as well? (second sentence on this page)


                15 Jul 2014
                1. User avatar

                  Warren Thompson

                  Hi William,

                  That's now done. Thanks for the catch, we're overhauling all the docs and hopefully getting to these things. Your help and patience is greatly appreciated!

                  Thanks again,


                  15 Jul 2014
  4. User avatar


    Can we run JIRA on multiple application servers?  The previous SME set us up with a warm standby.  I am hoping he just didn't investigate this, as it seems really surprising that a mission-critical, database-backed web application couldn't be scaled properly.




    13 Oct 2011
  5. User avatar

    Paul Stahlke

    How well does JIRA/JAVA take advantage of multi-core processors?  If I have a choice of a 4-core 3.2 GHz machine, or a 6-core 3.0 GHz machine, what will make our large JIRA instance run faster?  The raw CPU speed, or the greater number of cores?

    25 Apr 2012
  6. User avatar

    Roy Krishna [Atlassian]

    JIRA is generally not cpu-bound so it may not make much of a difference either way. You could look at getting the cheapest option out of those and then spend the difference on extra RAM and/or SSDs.

    Although there is a benefit to getting lots of cores and then using NUMA settings for GC. Also your DB might benefit, assuming it's running on the same box.

    26 Apr 2012
  7. User avatar

    Matt Doar (ServiceRocket)

    From Re: ScreenshotApplet throws ClassNotFoundException (com.atlassian.jira.screenshot.applet.ScreenshotApplet.class) it appears that the version of Java on the client side has to be before Java 7 for the screenshot application to work.

    30 Aug 2012
  8. User avatar


    It would be nice to mention that JIRA requires a mail server (either local or remote) to process the email notifications properly. Comments from the Using Gmail as a JIRA Mail Server article are quite helpful as an entry point to this topic.

    04 Sep 2012
  9. User avatar

    Charles Phillips

    '300MB – 1GB' for evaluation is... outdated at the least!  I could not get JIRA running with 1GB of memory, and it doesn't even pass along the Java memory error on launch.

    Looks like I'm not the only one:

    "...fresh install of JIRA 5.5.1 takes between 2.1 and 2.3 GB of RAM, with 0 issues and standard plugin set."

    I'm not sure what the point is of a 32-bit installation, if JIRA needs more than 1.2 GB of memory!

    Hope this saves someone else the hour I have lost trying out JIRA.

    03 Oct 2012
    1. User avatar

      Matt Doar (ServiceRocket)

      I reckon to use a machine with 4GB to run JIRA these days. 2GB almost works if nothing else is running.

      03 Oct 2012
    1. User avatar

      Mauricio Leyzaola

      As of July 2013 JIRA works with Ubuntu Server with 1 Gb. It is not light-speed sure, but it works.

      15 Jul 2013
  10. User avatar


    We are planning to have 500 projects and 2 Lakh issues in total. What would be the database size needed for this in production?

    24 Jan 2013
    1. User avatar

      Matt Doar (ServiceRocket)

      Start here: Scaling JIRA FAQ

      24 Jan 2013
  11. User avatar


    Can you run install JIRA and Crucible on the same server?

    21 Mar 2013
  12. User avatar

    Henry Zhang

    Does JIRA support 64-bit Oracle 11g database?

    17 Jun 2013
  13. User avatar


    Hopefully JIRA supports ARM-processors one day....

    13 Jan 2014
    1. User avatar

      William Crighton [CCC]

      AFAIK ARM is happily using JIRA today - so yea, JIRA supports ARM processors.

      15 Jul 2014
  14. User avatar

    Sameera Shaakunthala [non coroprate]

    Could someone please mention the version of Java I need to have? Should it be 1.8 or 1.7?


    08 Oct 2014
  15. User avatar

    Gordon Pettey

    This is rather misleading.

    • A JIRA installation running on a 64-bit Java platform may require additional memory (to run at a similar level of performance) to a JIRA installation running on a 32-bit Java platform.
      This is because a 64-bit Java platform's object references are twice the size as those for a 32-bit Java platform.

    Unless you're using a heap over 32GB, compressedOops makes that statement false.

    15 Jan 2015
  16. User avatar

    Kenny Silanskas

    I recently downgraded a SSD based droplet (using Digital Ocean) to a 64 Bit Ubuntu 2GB / Dual-Core CPU from a 64 Bit Ubuntu 4GB / Quad-Core CPU to save a little money since I am the only one using the instance and it has far less than this line states:

    For a small number of projects (10-20) with 1,000 to 5,000 issues in total and about 100-200 users, a recent server (multicore CPU) with 2 GB of available RAM and a reasonably fast hard drive (7200rpm or faster) should cater for your needs.

    In fact I am literally the only person accessing this system "concurrently" which is to say I might open another tab once in a while.

    Unfortunately, JIRA and Confluence crashed and Atlassian has been assisting but I'd tread carefully when using 2GB. Oddly enough, I went back to the original droplet size and it still fails. 

    I do love Atlassian's products but boy can they be resource heavy.

    08 Mar 2015
    1. User avatar

      Chris Colman

      When you use Spring and Hibernate together resource heaviness is just the beginning.

      Hopefully they'll switch to a more efficient Java ORM implementation in the future. They definitely exist - we've used one for almost a decade now without the resource heaviness and sluggish user response of apps that use the dreaded resource heavy combo.

      05 May 2015
  17. User avatar

    Chris Colman

    Will JIRA use much CPU or DB access while not rendering pages? We don't expect our usage to be high or the number of tickets to be high - just wondering if there are any background processes that run on a regular basis that might chew up these resources when idle.

    05 May 2015
Powered by Confluence and Scroll Viewport