On this page:
- JIRA Installation Directory
- JIRA Home Directory
JIRA Installation DirectoryThe 'JIRA installation directory' is the directory into which the JIRA application files and libraries have been unpacked (unzipped) when JIRA was installed. JIRA does not modify or store any data in this directory.
Important Files and Directories
This file tells JIRA where to find the JIRA Home Directory, as well as storing many other configuration settings. This file is modified by the administrator when installing JIRA Standalone (not using Windows installer) or Installing JIRA WAR-EAR.
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 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. Please see Where are the application server logs? for further details.
This file configures the OFBiz Entity Engine which JIRA uses to store persist data in a datasource. See Configuring the Entity Engine for JIRA.
This file is used for JIRA SSL configuration. See Running JIRA over SSL or HTTPS.
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 Unix, you would update this file:
See Increasing JIRA Memory for further details.
JIRA Home DirectoryThe 'JIRA home directory' contains key data that help define how JIRA works. This document outlines the purpose of the various files and directories in the JIRA home directory. (For information on specifying the location of the JIRA home directory, please see Setting your JIRA Home Directory .)
Tip: Another term for 'home directory' would be 'data directory'.
This directory contains application data for your JIRA instance, including:
- attachments (every version of each attachment stored in JIRA) — note, your JIRA administrator can define a custom attachments directory.
This does not affect manually generated backups, i.e. you must specify the target location for a manually generated backup.
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 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 Indexing in JIRA
- OSGi framework caches
These files are vital for JIRA performance and should not be modified or removed externally while JIRA is running.
Note: If you are running a high load JIRA instance, you may wish to consider moving your indexes from the default directory under JIRA home to another machine. The directory which holds your indexes is heavily accessed while JIRA is running. Hence, your JIRA instance may run more efficiently by hosting the indexes on the fastest disk available and reducing the number of other applications using the same disk to reduce access contention.
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.