Upgrading JIRA
There are several different ways to upgrade JIRA, and the method you choose to use depends on which version of JIRA you use and the type of environment you use it in. Use this table to determine which steps to follow to complete your JIRA upgrade:
If you need to move JIRA to a new server or use it in a new environment that has a different operating system, different database type or different location of attachment or index files, follow the instructions for Migrating JIRA to Another Server.
| Required Uptime (SLA) | Hardware/Software Change | Operating System | JIRA Package | Current JIRA Version | Upgrade Process |
High / Mission Critical This method is recommended for enterprise environments where extended or unplanned downtime might negatively impact the business. For information on upgrading to JIRA Data Center, please see Installing JIRA Data Center. | Any | Any | Any | Any | Upgrading JIRA with a Fallback Method |
Low – Medium If you use JIRA in a non-mission critical environment, depending on your specific installation details, you use either the safe (no downtime) or manual method to upgrade. If you are upgrading from JIRA 4.3.0 or later, you also have the option to use the upgrade capabilities built into the installer to perform a rapid upgrade of your existing JIRA installation - this method is the fastest way to upgrade - however due to its in-place upgrade method, having recent backups is crucial for this option. | Neither operating system, database or home directory will be changed. | MS Windows / Linux | Standalone | 4.3.0 or later | Upgrading JIRA Using a Rapid Upgrade Method |
| 4.2.x or earlier | Upgrading JIRA Manually | ||||
| WAR | Any | Upgrading JIRA Manually | |||
Solaris | Any | Any | Upgrading JIRA Manually |
If you plan to skip multiple major versions of JIRA when you upgrade, please review the Skipping Major Versions when Upgrading JIRA for important information on the recommended way to skip versions.