upgrade_Migrate JIRA configs
If you have modified properties in configuration files of your existing JIRA installation, make the same modifications in your new JIRA installation. However, because the properties in the configuration files may have changed between versions, you cannot simply copy the configuration files from your existing installation and replace the equivalent files in the new installation.
For each file you have modified in your existing JIRA installation, you need to manually edit each equivalent file in your new JIRA installation and re-apply your modifications. If a file is not present in your new JIRA installation (for example, osuser.xml
in recent JIRA versions), then simply copy that file over to your new JIRA installation.
The table below lists the most commonly modified files and their locations within your JIRA Installation Directory:
File | Location in 'recommended' (formerly 'Standalone') JIRA distributions | Location in JIRA WAR | Description |
---|---|---|---|
jira-application.properties |
|
| Location of the JIRA Home Directory and Advanced JIRA Configuration in JIRA 4.3.x and earlier. |
setenv.bat (Windows) or setenv.sh (Linux) |
| Application server's | |
osuser.xml |
|
| Modified if you have integrated LDAP with JIRA, integrated Crowd with JIRA, or if you are using a custom form of external user management or user authentication. |
seraph-config.xml |
|
| Modified if you have integrated Crowd with JIRA. |
server.xml |
| Application server's | Modified in the following situations:
|
The version-specific upgrade notes contain details on properties which may have changed in these commonly modified files.
In addition to the files above, you should also consider and/or perform the following configurations as part of the upgrade process:
- Using JIRA with Atlassian's Crowd? — If you are using Crowd with JIRA, configure your new JIRA to talk to Crowd as described in Integrating Crowd with JIRA.
- Remember to configure Crowd to grant JIRA's new hostname/IP access: Specifying an Application's Address or Hostname
- Allocating additional memory to JIRA — If you had previously allocated additional memory to JIRA, do the same for your new JIRA instance. For more information refer to Increasing JIRA memory.
- Plugins — For any plugins that you had installed in your old JIRA, download the plugin version for your new version of JIRA from the http://plugins.atlassian.com site.
- Character encoding — Ensure that character encoding (i.e. locale) is the same on the new and old locations. Your new version of JIRA may not function correctly if attachments are moved between two system with incompatible encoding.
- Customisations — If you had made any customisations (code, templates or configuration files), copy over compatible versions of these changes to the new JIRA. (The developers within your organisation who made the customisations to your old version will need to build and test equivalent changes for the new version, and provide you with the files to copy to your upgraded JIRA installation.)
- (Optional) Running JIRA on a different port — If your new JIRA is installed on the same machine as your old JIRA, you may wish to make sure it runs on a different port (in case you ever need to restart your old JIRA). See Changing JIRA's TCP Ports for details.