Documentation for JIRA 6.4 (This documentation includes the project navigation sidebar). Not using this? See below:
(JIRA 6.4 without sidebar documentation | JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

The 'JIRA Home Directory' contains key data that help define how JIRA works. This document outlines the purpose of the various files and subdirectories within the JIRA Home Directory.

If JIRA was installed using the automated Windows or Linux installers, the default location of the JIRA Home Directory is:

  • C:\Program Files\Atlassian\Application Data\JIRA (on Windows) or
  • /var/atlassian/application-data/jira (on Linux)

If you install JIRA from an archive file, the JIRA Home Directory can be any suitable location that is accessible by your JIRA installation. Typical example locations might be:

  • C:\jira\home (on Windows) or
  • /var/jira-home (on Linux or Solaris)

(warning) However, avoid locating the JIRA Home Directory inside the JIRA Installation Directory.

(tick) For information on specifying the location of the JIRA Home Directory, please see Setting your JIRA Home Directory.

Important Files

dbconfig.xml

This file (located at the root of your JIRA Home Directory) defines all details for JIRA's database connection. This file is typically created by running the JIRA Setup Wizard on new installations of JIRA or by configuring a database connection using the JIRA Configuration Tool.

You can also create your own dbconfig.xml file. This is useful if you need to specify additional parameters for your specific database configuration, which are not generated by the Setup Wizard or JIRA Configuration Tool. For more information, refer to the 'manual' connection instructions of the appropriate database configuration guide in the Connecting JIRA to a Database section.

jira-config.properties

This file (also located at the root of your JIRA Home Directory) stores custom values for most of JIRA's advanced configuration settings. Properties defined in this file override the default values defined in the jpm.xml file (located in your JIRA Installation Directory). See Advanced JIRA Configuration for more information.

(info) In new JIRA installations, this file may not initially exist and if so, will need to be created manually. See  Making changes to the jira-config.properties file for more information. This file is typically present in JIRA installations upgraded from version 4.3 or earlier, whose advanced configuration options had been customized (from their default values).

Important Subdirectories

data

This directory contains application data for your JIRA instance, including attachments (for every version of each attachment stored in JIRA).

export

JIRA will place its automated backup archives into this directory.

log

JIRA will place its logs into this directory. (Note: if the JIRA home directory is not configured, then the logs will be placed into the current working directory instead).

The logs will only start showing up once the first log message is written to them. For example, the internal access log will not be created util JIRA starts writing to it.

You can change the location of the log file using log4j.properties as described in the documentation on Logging and Profiling.

plugins

This is the directory where plugins built on Atlassian's Plugin Framework 2 (i.e. 'Plugins 2' plugins) are stored. If you are installing a new 'Plugins 2' plugin, you will need to deploy it into this directory under the installed-plugins sub-directory.

'Plugins 1' plugins should be stored in the JIRA Installation Directory.

This directory is created on JIRA startup, if it does not exist already.

caches

This is where JIRA stores caches including:

These files are vital for JIRA performance and should not be modified or removed externally while JIRA is running.

See Search Indexing for further details.

tmp

Any temporary content created for various runtime functions such as exporting, importing, file upload and indexing is stored under this directory.

You can remove files from this directory while JIRA is running, but we recommend that you shut down JIRA first before altering the contents of this directory.

  • No labels

7 Comments

  1. Anonymous

    Hi everyone i'm trying to check the storage available on Jira home/data, How can I do that?

    Anyone is more than welcome to help, Please.

    1. If you're on Windows this should help. On Linux, from the command line, navigate to JIRA home (/var/atlassian/application-data/JIRA by default) and run this command 'du -hd 1' (without apostrophe). The value at the bottom of the output that corresponds to the period is the total size of all data in that directory. I realize you've likely already solved this problem but others who see this may not have.

  2. Anonymous

    I have no "tmp" directory in jira.home, but a "temp" directory. Is this a typo or "tmp" and "temp" are equivalent?

    Thanks

  3. Those are two different directories. On Windows for example they resist in:

    "x:\Program Files\Atlassian\Application Data\JIRA\tmp"
    "x:\Program Files\Atlassian\JIRA\temp"

     

  4. Anonymous

    Hi, i have just a simple Question for my comprehension. 

    Can i delete every directory and file like "Attach.tar" in the directory jira_home\tmp? Because the size of this directory is too big on our System.

    thank for your help.

  5. Why, specifically, should we "avoid locating the JIRA Home Directory inside the JIRA Installation Directory."

    1. There are files in the installation directories that are custom to the installation, so it's not like the installation directories can be swapped in and out.
    2. I keep a copy of the data directory specific to each version of the installation when I upgrade; it would be a lot simpler if I could bury each home directory inside the installation directory, which makes for easy sym-linking and cloning.

     

  6. Any chance JIRA data will be moved to X:\ProgramData\Atlassian\JIRA in the future? The current place can not be backed up by our (current) backup solution Backblaze.