Upgrade Guide from Jira 7.6 to 7.13
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Purpose
To help provide a detailed guide to help with the upgrade process of large scale and business critical Jira environments to Jira 7.13.latest. Other methods for upgrade also exist, see here: Upgrading Jira application
Solution
Preparation
Before You Start
Check Jira 7.13 Supported Database Versions:
Oracle 12c
MySQL 5.5, 5.6, 5.7
PostgreSQL 9.3 (deprecated), 9.4, 9.5, 9.6
Microsoft SQL Server 2012, 2014, 2016
Check plugin compatibility
Within your current installation of Jira, go to Administration > Add-ons > Manage add-ons. At the bottom of the page, there is a link for Jira update check.
Third-party apps may have upgrade requirements, please ensure to be familiar with these requirements as it may require additional intermediate upgrade steps
Check other Atlassian product compatibility, see Application links matrix. Jira 7.13 uses AppLinks 5.4.5 - based on that, minimal versions for other applications are:
Bamboo 6.6+
Confluence 6.8+
Crucible/Fisheye 4.4+
Bitbucket 5.9+
Review the Recommended Readings (links to the right)
Optimize the Upgrade process
These steps will help reduce the amount of time needed for the full upgrade process to complete:
Starting Jira 7.9, there is an upgrade task that will migrate Developer Summary data from one table to another as per JSWSERVER-15748 - DVCS Plug-in doesn't purge caches from 'entity_property' table. This process can take longer when the data in the previous table is very large (1+ million entries). To help reduce the total upgrade time;
a manual copy from the old entry of
entity_propertytable can be performed prioror, apply the workaround to delete anything older than 30 days worth of data as per the bug report
or, for Oracle DB, set UNDO Tablespace to autoextend in order to prevent UpgradeTask failure
Prepare server.xml to be compatible with Jira 7.13 prior to the upgrade. See
Changing server.xml to handle requests with special characters
Testing
We strongly recommend performing your upgrade in a test environment first. Do not upgrade your production Jira server until you are satisfied that your test environment upgrade has been successful. If you have any problems with your test environment upgrade which you cannot resolve, create an issue at our support site so that we can assist you.
Details: Upgrade Checklist and Creating a test environment for Jira.
Upgrade Steps for Jira Software
Before proceeding - third-party apps may have upgrade requirements, please ensure to be familiar with these requirements as additional intermediate upgrade steps may be required.
Upgrading to Jira Software 7.13.latest
Stop the current Jira instance.
Make a copy of the Jira database to a new database.
Make a copy of the Jira_HOME to a new location.
Remove the
plugins/folder located in the new Jira_HOME.Performing the upgrade without plugins has been found to be more reliable and faster.
If you run Jira Data Center, also remove (and backup) the
<Shared>/plugins/folder.
Modify the
dbconfig.xmlfile in the newly copied Jira_HOME.Configure the file to point to the newly copied database.
Extract your Jira Software 7.13.latest to a new target Jira_INSTALL folder.
Configure your Jira Home folder path and point to the newly copied Jira_HOME.
Copy memory allocation settings and any other custom parameters you deem necessary from the previous installation to the new one, as described in Setting properties and options on startup.
Start Jira and review the logs to ensure the upgrade completes successfully.
If using Service Management, navigate to Cog Icon > Applications > Version & Licenses.
Update/Install the Jira Service Management application to the latest version.
Re-install plugins via file the Cog Icon > Add-ons > Find new add-ons.
If preferred, upload the add-ons manually via Cog Icon > Add-ons > Manage add-ons > Upload add-on. ⚠️ Not all plugins are compatible with Jira 7.13.latest. Ensure to verify compatibility first!
Test and ensure that the instance is functioning to satisfaction.
Restart Jira.
Perform a Lock Jira and rebuild the index.
Was this helpful?