Important directories and files
Jira installation directory
Jira does not modify or store any data in this directory.
Important files and directories
The directories/files described below are found under different sub-directories of the 'Jira Installation Directory', depending on whether you have installed a recommended Windows, Linux or Archive Jira. Please substitute the following directories for the
<Jira-application-dir> placeholder (used throughout the rest of this section), as follows:
- 'Recommended' distributions — the
atlassian-jirasubdirectory of the 'Jira Installation Directory' installed using the 'Windows Installer' and 'Linux Installer', and there associated installations from archive files (.zip and tar.gz respectively).
The default installation directory on Linux is:
This file tells Jira where to find the Jira application home directory.
Be aware that your Jira home directory defined in this file can be overridden. See Setting your Jira application home directory for more information.
This file stores the default values for Jira's advanced configuration settings and should not be modified. The default values of properties in this file are customized (i.e. overridden) by redefining them in either the
jira-config.properties file (in your Jira application home directory) or the Jira database (via the Jira administration area). See Advanced Jira configuration for more information.
This is the directory where plugins built on Atlassian's Plugin Framework 1 (i.e. 'Plugins 1' plugins) are stored. If you are installing a new 'Plugins 1' plugin, you will need to deploy it into this directory.
'Plugins 2' plugins should be stored in the Jira application home directory.
Jira's logging configuration file. See Logging and profiling.
The actual log files generated by Jira can be found in the following locations:
- Jira application log —
- Application server log — generally the application server log file can be found under the
logsdirectory. However, this can vary depending on the application server you are running.
This file configures the OFBiz Entity Engine, which Jira uses to store persistent data in a data source.
The sub-directories/files described below are found under the root of the Jira application installation directory.
This file is used for Jira SSL configuration. See Running Jira applications over SSL or HTTPS.
These files include garbage collection (GC) logs that can be used to monitor the performance of Jira applications. The log statements indicate when Java is collecting garbage, how long this process takes, and which resources can be freed. The files are created automatically, and then overwritten if the maximum number of files (5) is reached. The timestamp indicates when the Jira session related to the logs was started. For more info, see Using garbage collection logs.
The file used to edit JAVA_OPTS memory settings will depend on the method used to install Jira, as well as the operating system used for your installation.
For example, if you are running Jira on Tomcat in Windows (manual startup), you would update the following file:
whereas for Jira on Tomcat in Linux/Unix, you would update this file:
See Increasing Jira memory for further details.
Jira home directory
C:\Program Files\Atlassian\Application Data\JIRA(on Windows) or
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)
However, avoid locating the Jira home directory inside the Jira application installation directory.
For information on specifying the location of the Jira home directory, please see Setting your Jira application home directory.
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).
This directory contains application data for your Jira instance, including attachments (for every version of each attachment stored in Jira).
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
log4j.properties 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
'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:
- Lucene indexes - see Troubleshoot index problems in Jira server
- OSGi framework caches
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.