Downgrading an Add-on to an Earlier Version
If an update to an app (also known as an add-on or plugin) seems to break the app or cause other problems in the host application, you may need to remove it or revert it to an earlier version.
Before starting, check the plugin documentation if there weren't any internal data structure changes that could block the downgrade. When this happens, you will need to get detailed instructions from the vendor to do the downgrade or you will need to do a full rollback of your environment, restoring the Database, Jira home, shared directory (cluster).
If there is no restriction for the downgrade, you can do so by replacing the app's JAR file on disk.
Before starting, get the earlier plugin version from Atlassian Marketplace. Download links for the earlier versions appear in the version history section of the app page.
Once you have the JAR file of the version you want to apply, follow the instructions for updating UPM by file replacement to downgrade the add-on version. The downgrade procedure for any app is the same as for UPM.
For Confluence, you must first remove the app artifact from the database. For more information, see the How to manually remove malfunctioning apps article in the Confluence Knowledge Base.