Jira hosting: Server, Data Center
Upgrading Jira add-ons is generally a straightforward process.
However, we do recommend you make a full Jira backup and read this page so that you understand the whole process and therefore minimize the risk of failure.
Backup your data
Before making a major The Scheduler upgrade, we recommend you take a backup of your Scheduled Issues. While not strictly necessary, this is an additional safety measure in case of any migration problem.
Our app has built-in Export / Import to .xml features. Here you can read more about it:
Data migration
Whenever you install a new version of our add-on, Jira automatically migrates your data to the new format. There is no need to manually migrate any data - after the new version is installed, your data should still be there.
Minor version upgrades
If you're upgrading a minor version release (such as The Scheduler 5.0 to The Scheduler 5.1), there are no additional actions required - simply update using UPM or by uploading a JAR file and you should be good to go. It is, of course, still recommended to take a backup before doing so.
Since version 5.3.0 we have introduced a new mechanism for Jira Administrators to showing "What's new" in the app. Now you can easily make adjustments to important changes or send notes with direct links to documentation to your users, you will see this page after upgrade:
Upgrading from previous The Scheduler versions
If you're upgrading from the previous The Scheduler version, we recommend you upgrade to the latest available version before installing The Scheduler 5.x.
The following upgrade paths are recommended:
If you're currently running The Scheduler 3.x (JIRA 6.x)
Make sure you're running The Scheduler 3.3.7 (the latest add-on version for JIRA 6.x)
Upgrade JIRA first, then install the latest The Scheduler add-on version (you don't need to install 4.x, go straight to latest 5.x version)
After upgrade In some cases you might experience a 404 error, when reaching to Access Manager page, here is a how to article how to fix it: Upgrading The Scheduler from 3.x to 5.x
If you're running The Scheduler 4.x
Make sure you're running The Scheduler 4.3.6 (the latest 4.x version)
Install the latest The Scheduler add-on version