Skipping major versions when upgrading JIRA applications
Upgrading JIRA applications
- Upgrading JIRA applications manually
- Upgrading JIRA applications with a fallback method
- Upgrading JIRA applications using a rapid upgrade method
- Skipping major versions when upgrading JIRA applications
- Disabling auto-export
- Rolling back a JIRA application upgrade
- Migrating JIRA applications to another server
- Establishing staging server environments for JIRA applications
On this page
Related content
- No related content found
If you're upgrading from a version of JIRA earlier than 7.0, you should consult the Migration hub. The release of JIRA 7.0 contained functionality that affects your user management, application access and log in permissions, and your JIRA installations setup, and it's very important that you understand the requirements and the implications before you upgrade. The Migration hub has all this information in one handy space.
To upgrade from early versions of JIRA to newer versions, you must upgrade to JIRA 4.4.5 before upgrading to a later version.
Follow these steps to skip major versions as you upgrade JIRA:
- Prepare: Read the upgrade guides for all the major versions between your current version and the version to which you are upgrading. You can read about important changes between versions in the Important Version-Specific Upgrade Notes.
- Upgrade to an interim version: Upgrade to JIRA 4.4.5 following these Upgrading JIRA with a Fallback Method instructions.
- Upgrade to the new version: Upgrade to the new version of JIRA following these appropriate instructions. Use the table on Upgrading JIRA page to determine which method is appropriate for your environment.
Last modified on Sep 5, 2017
Related content
- No related content found
Powered by Confluence and Scroll Viewport.