Make sure you have completed the steps in Preparing for the upgrade. These are mandatory pre-requisites, and are essential for a smooth upgrade.
If you need help choosing the right version for you, head to the upgrade matrix to get a quick run down of features, supported platforms, and technical upgrade notes for all Jira versions.
Omit this step if you're upgrading your Data Center with zero downtime.
Stop Jira on all nodes in the cluster. We also recommend that you configure your load balancer to redirect the traffic away from Jira until the upgrade is complete on all nodes.
To avoid upgrading each of the nodes separately, you’ll just upgrade one of them, and make its installation directory a template. Then, you’ll copy this template to remaining nodes. You can choose any node here.
Jira Software
Jira Service Management
If you're upgrading both Jira Software and Jira Service Management, upgrade Jira Software only. You'll later upgrade Jira Service Management directly in Jira, without a separate installer.
The installation wizard will guide you through the upgrade process.
·I'm using Windows...
·I'm using Linux...
The wizard notifies you of customizations in the Jira installation directory. Make a note of these as you'll need to reapply them later.
Your current customizations will be overwritten, but you can later copy them from your backups.
Starting Jira here won't affect your upgrade in any way, but Jira needs to be shut down to complete the remaining steps. Once you complete them, you can go back to the wizard and start Jira.
If you're using an Oracle or MySQL database, download a new JDBC driver. For other databases, you can omit this step.
If the driver is up to date, you can also copy it from your previous version.
Oracle: JDBC driver 19.3 (ojdbc8)
MySQL: MySQL Connector/J 5.1 driver.
While using Jira, you’ve probably added some custom modifications to Jira files. These may include connection details, settings related to memory allocation, or other JVM arguments. In this step, you need to re-apply the same modifications to the new files by copying them from your backups.
Make sure you don't just copy over the old files, as the 'native' settings they contain might have changed between the Jira versions.
During the upgrade, the wizard migrated the following from your existing Jira installation:
·JVM_SUPPORT_RECOMMENDED_ARGS
·JVM_MINIMUM_MEMORY
·JVM_MAXIMUM_MEMORY
·JIRA_MAX_PERM_SIZE
Apart from the above, you need to re-apply all other modifications. Here are the most important files:
We'll make another check on Jira startup and will show you all the files you might have skipped that still contain changes that have not been copied over. Then you'll be able to click to automatically copy the changes over.
Note that the check will only be run on the following configuration files:
- <jira-home-directory>/atlassian-jira/ directory
- <jira-home-directory>/conf/server.xml
- <jira-home-directory>/bin/setenv.sh
and the automatic transfer will only be supported for ATST plugin 1.20.0 and later.
To automatically transfer the changes, the installer copy of the modified file needs to be the same as in the version you're upgrading to.
If you're upgrading from Jira 7.x to Jira 8.x we recommend changing the pool-max-size parameter to 40 in your dbconfig.xml before the upgrade. Leaving the default of 20 can sometimes lead to “ResultSet Closed” errors during re-indexing on 8.x. For information on implementing the change, see Tuning database connections.
This step is recommended when upgrading from Jira 7.x to Jira 8.x. If you're already on the 8.x line, you can omit this step.
Because of the changes to indexes that we've introduced in Jira 8.0, the index from any earlier Jira version will be incompatible after the upgrade. To create a new index, Jira will trigger an automatic reindex right after you start it. To avoid reindexing twice (after startup and after upgrading your apps), you can disable the automatic reindex, and run the second one later, whenever you’re ready.
Edit or create the following file:
<jira-home-directory>/jira-config.properties
Add the following line, and save the file:
upgrade.reindex.allowed=false
Complete these post-upgrade steps only on the first node (the one you've just upgraded). The remaining nodes will later download the upgraded apps and index from the shared directory.
Start your new Jira version, and connect it to the database.
If you've missed any file with custom changes that have not been copied over, you can automatically copy the changes over now.
Note that the check for file changes is only be run on the following configuration files:
- atlassian-jira/ directory
- conf/server.xml
- bin/setenv.sh
and the automatic transfer is only be supported for ATST plugin 1.20.0 and later.
To automatically transfer the changes, the installer copy of the modified file needs to be the same as in the version you're upgrading to.
After the changes have been copied over, you'll be prompted to restart Jira.
After a successful upgrade, you should see the post-upgrade landing page. It has some useful information about the new version, as shown below.
If you're using Jira Service Management, you can update it directly in the UI, without downloading a separate installer.
) > Applications > Versions and licenses.Now you can upgrade apps that had the Compatible once both are updated status. If you need more information about the statuses and apps in general, see Preparing for the upgrade.
) > Manage apps > Manage apps.Upgrading apps in a DC cluster
When upgrading apps, each node will pull the the most recently modified app jar file from the shared home on reboot.
To determine the file version, Jira uses the <version> value inside atlassian-plugin.xml. If there are multiple <version> values, Jira uses java.lang.String#compareTo to compare the different values.
Reindex Jira to recreate your index. This step might take some time, depending on how many issues and apps you have.
) > Indexing, and run Lock Jira and rebuild reindex.In this step, you'll copy the new installation directory with all the modifications you did so far. This will give you a template that you'll later copy to other nodes.
By now, you should have the ready Jira template, and upgraded add-ons and index data available in the shared directory. In this step, you'll copy the template to other nodes and start them one by one.
Joining the cluster
You can check if the upgraded nodes are joining the cluster by going to Administration (
) > System > System info, and scrolling down to the Cluster nodes section.
You've upgraded Jira to a new version.
© Copyright 2000-2023 COGITO SOFTWARE CO.,LTD. All rights reserved
