Upgrading JIRA applications
There are several 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 |
100% uptime This method is recommended if you're running JIRA Software Data Center 7.3 or above, and require your JIRA instance to be available throughout the upgrade. | Neither operation system, database or home directory will be changed. | MS Windows / Linux | JIRA Software Data Center | JIRA Software Data Center 7.3 and above | Managing zero downtime upgrades |
High / Mission Critical This method is recommended for enterprise environments where extended or unplanned downtime might negatively impact the business. | 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 installer or manual method to upgrade. | Neither operation system, database or home directory will be changed. | MS Windows / Linux | Standalone | 4.3.0 or later | Upgrading JIRA using the installer |
| 4.2.x or earlier | Upgrading JIRA manually | ||||
Solaris | any | any |