1. 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.
2. Review the release notes and upgrade guide
Check the release notes for anything you think would impact your users.
Tip: Use the Component column in the release notes to easily identify which parts of the application will have most impact on your work processes, so that you can focus quick checks in the features your users frequently use.
Hotfix releases almost never contain breaking changes.
The table below lists R4J versions that require preparation due to breaking changes. Versions not listed here are safe to upgrade or downgrade as needed.
R4J version | Upgrade guide | Supporting articles / Important notes |
|---|---|---|
R4J 4.6.x vs 4.7.x performance benchmark results Loading issues and errors encountered after tree data migration | ||
“Expand all“ is removed. The feature comes back at 4.8.0. | ||
Summary of functions affected by revisions restructure in R4J 4.5 | ||
Coverage view filter migration. Already EOL. If further support is needed, contact our service desk. |
3. Backup your instance data
4. Test the R4J version upgrade using a test or staging instance
Based on your reviews done, do a quick check how the plugin works on your test and staging instance. It would be best if these instances have similar configurations as your production environment.