Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

Due to security vulnerabilities in JIRA that have been fixed in JIRA 4.1.1 and later (and in earlier versions of JIRA that have been fixed via patches available from JIRA Security Advisory 2010-04-16), it is now a mandatory requirement to explicitly permit modification to JIRA's file path settings using the first method below.

Enabling Modification to JIRA's File Path Settings

To change the locations for storing file attachments, backups, etc, you will need to do the following:

  1. Shutdown JIRA.
  2. Open the jira-application.properties file in a text editor. Refer to Advanced JIRA configuration with jira-application.properties for details.
  3. Locate the jira.paths.set.allowed variable in this file.
  4. Set this variable's value to true.
  5. Restart JIRA.
    (info) After saving directory name changes via the JIRA user interface, it is strongly recommended that you follow the procedure for Securing JIRA's File Path Settings (below) as this will minimise the risk of your JIRA instance being compromised by security-related attacks.

Securing JIRA's File Path Settings

To secure the locations for storing file attachments, backups, etc, you will need to do the following:

  1. Shutdown JIRA.
  2. Open the jira-application.properties file in a text editor. Refer to Advanced JIRA configuration with jira-application.properties for details.
  3. Locate the jira.paths.set.allowed variable in this file.
  4. Do one of the following:
    • Set the jira.paths.set.allowed variable to false (that is, jira.paths.set.allowed=false)
    • Set the jira.paths.set.allowed variable to anything other than true or leave its value blank (that is, jira.paths.set.allowed= )
    • Either delete the jira.paths.set.allowed property or comment it out (for example, #jira.paths.set.allowed=disabled)
  5. Restart JIRA.
  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.