1. Review the release notes and upgrade guide
Check the release notes for anything you think would impact your users.
...
We strongly recommend to have a test or staging instance setup, which is as similar as possible to your production instance. This includes server and database configuration and properties, user/admin permissions, as well as a copy of the production data.
3. Plan tasks for the upgrade outside of business hours
Third-party plugins may have some effect to other plugins or Jira itself. For any upgrade, it’s safest to always plan outside of business hours in case anything goes wrong.
4. Backup your instance data
You should have an up-to-date backup to allow you to roll back the database in the very unlikely event that some sort of data corruption results from the upgrade.
5. Perform the R4J version upgrade in your production instance
| Info |
|---|
It is important to do a quick test of the upgrade on your production instance. Based on the results, finalize your decision to remain with the version or rollback roll back to a backward compatible version. |