Upgrading JIRA applications

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.

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

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 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 operation 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


any any Upgrading JIRA manually


  • We strongly recommend that you upgrade to the latest production version available. If you upgrade to an older version of JIRA, it may contain security vulnerabilities that were patched or fixed in subsequent versions. If you have to upgrade to an older version, check if there are any security advisories that apply to the version.
  • 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.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport