Those versions are compatible. So if these are getting disabled, it tends to be for another reason. When upgrading Jira, commonly the setenv file can be overwritten. If you're using a linux/unix platform, and/or starting Jira from the .bat/.sh files, then overwriting this file can revert your Jira installation to use the default memory settings. You might need to follow Increasing Jira memory once more to make sure that your Jira instance has the needed amount of memory to start up all these plugins.
Once that is done, you can then run a SQL command such as
select * from pluginstate;
This will list all the plugins that have been disabled within the database. You can then clear the entries from this table as one way to allow Jira to load these plugins upon the next start up.
If you are not sure which values to remove from this table, please let me know the results and I will try to guide you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.