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

Install

JIRA running on Mac OS should only be used for evaluation purposes!

Mac OS 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 is packaged with a JDK optimised for its hardware.

Please note:

  • If you encounter problems with your JIRA server running on Mac OS, they may not be fixed as we do not test JIRA with unsupported Java platforms.
  • However, JIRA users can still access your JIRA server through a supported browser on Mac OS.

To install JIRA Standalone on Mac OS, follow these steps:

Before you begin

Please ensure that you have set JAVA_HOME. (You don't need to install Java as it comes with Mac OS.)

1. Download and Install JIRA Standalone

(info) Before you begin, you may want to watch the installation video.

  1. Download the JIRA Standalone TAR (.GZ) file here.
  2. Unzip the downloaded file.

2. Set JIRA Home

To specify the location of your JIRA Home Directory, either:
  • Edit the jira-application.properties file (see the JIRA Installation Directory page to find where this file is located), add a 'jira.home' property and set it to your desired location for the JIRA home directory.
  • Set an environment variable named JIRA_HOME in your operating system whose value is the location of your JIRA home directory. To do this, do one of the following:
    • Enter the following command at a shell/console prompt before running JIRA:
      • export JIRA_HOME = /path/to/jira/home
    • Specify the command above in a script used to start JIRA.
You can specify any location on a disk for your JIRA home directory. Please be sure to specify an absolute path.

Please note that you cannot use the same JIRA home directory for multiple instances of JIRA. We recommend locating your JIRA Home Directory completely independently of the JIRA Installation Directory (i.e. not nesting one within the other) as this will minimise information being lost during major operations (e.g. backing up and restoring instances).

3. Start JIRA

A dedicated user should be created to run JIRA, as JIRA runs as the user it is invoked under and therefore can potentially be abused. Here is an example of how to create a dedicated user to run JIRA in Linux/Solaris:

$ sudo /usr/sbin/useradd --create-home --home-dir /usr/local/jira --shell /bin/bash jira

Ensure that only the following directories can be written to by Tomcat:

  • logs
  • temp
  • work
  • database (this directory will be created the first time you run JIRA)
  • your JIRA Home directory

See also Tomcat security best practices

Run bin/startup.sh to start JIRA.

JIRA will be launched in a black 'Tomcat' window (do not close this window). Wait until the startup messages have finished.

To access JIRA, go to your web browser and type this address: http://localhost:8080.

If JIRA does not appear, you may need to change the port that JIRA runs on.

If something goes wrong, please verify that Java is installed correctly. If the problem persists, please contact us — we're happy to help.

4. Run the Setup Wizard

See Running the Setup Wizard.

Next Steps

  • See JIRA 101 to start creating Projects, creating Users, and customising your JIRA instance.
  • By default, JIRA Standalone uses the standard Tomcat port (i.e. 8080). If you need another application to run on that port, either now or in the future, please see Changing JIRA Standalone's port.
  • As part of its installation process, JIRA Standalone automatically installs, configures and connects itself to an HSQLDB database. This is fine for evaluation purposes, however HSQLDB is prone to data corruption. For production installations, we strongly recommend that you connect JIRA to an external database.
  • To get the most out of JIRA, please see Optimising Performance.



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.