Advanced Jira application configuration

Jira has a number of advanced configuration options, each of which is defined as an individual property (or 'key' associated with a value). These key-value pairs are stored in one of three areas for use by Jira:

The Jira database

The values of a small number of most commonly edited advanced configuration options are stored in the Jira database. These values can be edited from the Advanced Settings page of Jira's administration area. To access the values for editing, see Configuring Jira options.

Once any of these properties' values are changed, they become effective immediately.

The file

Custom values for Jira's remaining advanced configuration options (i.e. not stored in the Jira database) are stored as individual key-value pairs in a file called (located in the Jira application home directory). Typically, these options are of little interest to most Jira system administrators. While these key-value pairs can be edited, Jira must be restarted for any changed values to take effect.

Example contents to demonstrate format
jira.projectkey.warning = testwarning
jira.projectkey.description = testdescription

(info) In new Jira installations, this file may not initially exist and if so, needs to be created manually. For more information about editing the file, see Edit the file in Jira server.

The jpm.xml file

Default values for all* of Jira's available advanced configuration options are stored in a file called jpm.xml (located in the <jira-application-dir>/WEB-INF/classes subdirectory of the Jira application installation directory). These default values are only used by Jira if a property's value has not already been customized in either the Jira database (via Jira's 'Advanced Settings' page) or the file.

(warning) The jpm.xml file should not be edited because any values that you customize in it will not be migrated automatically during subsequent Jira upgrades. To change the value of a property for an advanced configuration option in Jira, override the value of this property by redefining it in either:

  • The Jira database (via Jira's 'Advanced Settings' page).
  • The file.

* Jira recognizes a small number of properties, which can be set in your file but have no definition in the jpm.xml file. These properties:

  • typically represent advanced configuration options that are disabled when they are not defined in your file and
  • when not specified in your file, typically affect Jira's behavior differently to when they are specified in your file with no value.

Making changes to the file

  1. Shut down Jira (for example, by executing either the /bin/ or \bin\stop-jira.bat file in your Jira application installation directory, or by stopping the Jira service).
  2. Open the file (located at the root of your Jira application home directory) in a text editor.
    (warning) This file may not exist if you are using a new Jira installation or an upgraded Jira installation where your previous Jira version(s) had never been customized. If this file does not exist, create it using a text editor.
  3. Edit the appropriate properties in this file.
    (tick) Editing tips:
    • To determine the default value of a property whose value you wish to redefine, search for that property in the <jira-application-dir>/WEB-INF/classes/jpm.xml file (of your Jira Installation Directory). The default value is defined in the <default-value/> sibling element of the relevant property's <key/> element.
    • To override a property's default value in jpm.xml (which is not already defined in your file or available on the 'Advanced Settings' page):
      1. Copy the value of the relevant property's <key/> element from the jpm.xml file to the file.
      2. In the file, add an '=' after that property's key, followed by your custom value.
    • To disable a custom property's value in the file, either 'comment out' the property with a preceding '#' symbol or remove the property from the file.
  4. Save your modifications to the file.
  5. Restart Jira.

See also

Setting properties and options on startup — for changes like setting available memory, disabling email, etc.

Last modified on May 29, 2018

Was this helpful?

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