documentation on how to change the secure paths inside JIRA Home (PUBLISHED BUT MOST LIKELY NEED TO AMEND)

see http://jdog.atlassian.com/browse/JRADEV-1384

Also see JRADEV-2082 With JIRA secure path change we are providing user no info about the directory for "Create issues from local files" service:

• http://jdog.atlassian.com/browse/JRADEV-2082

Behaviour now - JIRA 4.2 will ignore the following JIRA 4.1.1 'lock-down' properties in the jira-application.properties files:

• jira.paths.safe.backup.path=/to/some/safe/path
  and
• jira.paths.set.allowed=true

This means that all 'secure paths' in JIRA 4.2 will be located within the JIRA Home Directory (i.e. no 'Custom Directory' option is provided through the UI for Backups, Search Indexes and Attachments anymore).
Custom Directories can only be specified through the JIRA admin UI and are stored in the database.

When you restore a backup though, JIRA knows and respects the location of any old Search Index and Attachments directories, since this information is stored in the XML backups themselves.