Jira application home directory

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

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 application installation directory.

tip/resting Created with Sketch.

For information on specifying the location of the Jira home directory, please see Setting your Jira application home directory.

Important files


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 Connecting Jira to a database.


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 application installation directory). See Advanced Jira configuration for more information.

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


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


General purpose export directory used by data pipelines and support zips.


Jira will place its automated backup archives into this directory.


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 log4j2.xml as described in the documentation on Logging and profiling.


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 application installation directory.

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


This is where Jira stores caches including:

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

Indexing caches are stored in the following directories: 

  • <sharedhome>/caches/indexesV2/snapshots (cluster only): the main directory where Jira stores all index snapshots that are created:
    • on full reindex completion
    • on request of node joining cluster
    • on admin request made on admin panel
    • on complete import store location
    • by scheduled index backups. 

      Snapshots from this directory are picked when being replicated to the secondary home and a new node joins the cluster on admin request (when the admin starts a new Jira instance with correctly configured cluster-specific files.)

  • <localhome>/caches/indexesV2: the directory where indexes are stored.

See Search indexing for further details.


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.

Last modified on Mar 26, 2024

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.