There is not a one click solution to upgrading Jira Server. The process can be quite complex depending on your environment, the plugins you use with Jira, your hardware, etc.
There are actually a couple of different ways to upgrade Jira as explained in Upgrading Jira Applications
The steps to follow are different depending on which method you choose.
In most cases I recommend the use of the Fallback method to upgrade Jira. This is because it is the easiest way to revert/undo the upgrade attempt should things not work exactly as expected. The drawback of this method is that you have to setup a clone of your existing instance first, so this requires more time and effort up front to setup a perfect clone of your existing instance. In most upgrades of Jira, a lot of users find the plugins that Jira is using might need to be updated before either they can function or sometimes these older plugins can prevent Jira from starting during an upgrade.
Atlassian recommends using a Staging Server as a means to test out an upgrade before you do this to a production instance of Jira. This kind of setup would require you to clone the database, and clone all the contents of the $JIRAHOME folder in order to mimic your existing install. This can be helpful to understand the pitfalls and problems you might encounter when you then try to upgrade your existing instance.
We have Jira on a Virtual Machine. Before the upgrade we will make a snapshot of the VM and after if there is a problem during the install we can return to the snapshot.
We want to use the installer of the "UPDATE JIRA SOFTWARE SERVER" page first. We want a simple process.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG