Does my post-upgrade fix make sense?

Question

We are experimenting with an upgrade from v7.5.2 to v8.1.0 in a lab environment.  Until I did the following in the back-end we couldn't see tickets in the dashboard and couldn't create issues.  Various documents like https://confluence.atlassian.com/jirakb/cannot-create-issues-300814318.html suggested that I try disabling plugins.  So I renamed the following plugins and did another re-index job after restarting jira.  This seems to have fixed the problems.  Is this indeed the correct fix?

installed-plugins]# for P in plugin.[0-9]*; do mv -v "$P"{,.DISABLED}; done
`plugin.2473085602115002746.jira-importers-plugin-6.0.30.jar' -> `plugin.2473085602115002746.jira-importers-plugin-6.0.30.jar.DISABLED'
`plugin.2625373324686971006.jira-barchart-gadget-plugin-3.4.jar' -> `plugin.2625373324686971006.jira-barchart-gadget-plugin-3.4.jar.DISABLED'
`plugin.268714745576743079.plugin-jira-1.13.1.jar' -> `plugin.268714745576743079.plugin-jira-1.13.1.jar.DISABLED'
`plugin.2719144173565820765.jira-suite-utilities-2.1.0.jar' -> `plugin.2719144173565820765.jira-suite-utilities-2.1.0.jar.DISABLED'
`plugin.3105158680079654947.jira-calendar-plugin-4.0.3.jar' -> `plugin.3105158680079654947.jira-calendar-plugin-4.0.3.jar.DISABLED'
`plugin.3247878658395186964.atlassian-universal-plugin-manager-plugin-2.14.2.jar' -> `plugin.3247878658395186964.atlassian-universal-plugin-manager-plugin-2.14.2.jar.DISABLED'
`plugin.3350881165095751932.jira-importers-plugin-5.0.2.jar' -> `plugin.3350881165095751932.jira-importers-plugin-5.0.2.jar.DISABLED'
`plugin.3498747934882617952.jira-quick-subtasks-4.7.0.jar' -> `plugin.3498747934882617952.jira-quick-subtasks-4.7.0.jar.DISABLED'
`plugin.3696319434988378466.atlassian-universal-plugin-manager-plugin-2.22.17.jar' -> `plugin.3696319434988378466.atlassian-universal-plugin-manager-plugin-2.22.17.jar.DISABLED'
`plugin.4056292624721077725.jira-toolkit-0.35.14.jar' -> `plugin.4056292624721077725.jira-toolkit-0.35.14.jar.DISABLED'
`plugin.4162145059525863261.atlassian-universal-plugin-manager-plugin-2.14.5.jar' -> `plugin.4162145059525863261.atlassian-universal-plugin-manager-plugin-2.14.5.jar.DISABLED'
`plugin.459494202176921905.column-order-7.0.2.jar' -> `plugin.459494202176921905.column-order-7.0.2.jar.DISABLED'
`plugin.481032667188317043.jira-misc-custom-fields-1.7.2.jar' -> `plugin.481032667188317043.jira-misc-custom-fields-1.7.2.jar.DISABLED'
`plugin.503281980836878068.jiracomponentwatcher-2.5.1.jar' -> `plugin.503281980836878068.jiracomponentwatcher-2.5.1.jar.DISABLED'
`plugin.5785530407758691342.repeating-issues-0.11.3.jar' -> `plugin.5785530407758691342.repeating-issues-0.11.3.jar.DISABLED'
`plugin.5908390412372613602.jira-bamboo-plugin-5.1.6.jar' -> `plugin.5908390412372613602.jira-bamboo-plugin-5.1.6.jar.DISABLED'
`plugin.5966840448982726471.jira-timesheet-plugin-3.0.8.8.jar' -> `plugin.5966840448982726471.jira-timesheet-plugin-3.0.8.8.jar.DISABLED'
`plugin.6201117370481411903.jira-fisheye-plugin-6.1.1.jar' -> `plugin.6201117370481411903.jira-fisheye-plugin-6.1.1.jar.DISABLED'
`plugin.6253401572949369134.jira-charting-plugin-2.3.0.jar' -> `plugin.6253401572949369134.jira-charting-plugin-2.3.0.jar.DISABLED'
`plugin.6326106493697994895.jira-misc-workflow-extensions-5.0.6.jar' -> `plugin.6326106493697994895.jira-misc-workflow-extensions-5.0.6.jar.DISABLED'
`plugin.6756458727880155757.jira-importers-plugin-5.0.4.jar' -> `plugin.6756458727880155757.jira-importers-plugin-5.0.4.jar.DISABLED'
`plugin.7173029130823681414.jira-fisheye-plugin-5.0.13.jar' -> `plugin.7173029130823681414.jira-fisheye-plugin-5.0.13.jar.DISABLED'
`plugin.8393261003246641981.atlassian-universal-plugin-manager-plugin-2.20.7.jar' -> `plugin.8393261003246641981.atlassian-universal-plugin-manager-plugin-2.20.7.jar.DISABLED'
`plugin.8758135002663892993.jira-importers-bitbucket-plugin-1.0.4.jar' -> `plugin.8758135002663892993.jira-importers-bitbucket-plugin-1.0.4.jar.DISABLED'
`plugin.9097448856433534692.atlassian-universal-plugin-manager-plugin-2.18.2.jar' -> `plugin.9097448856433534692.atlassian-universal-plugin-manager-plugin-2.18.2.jar.DISABLED'

Jimmy Seddon · Answer

Hi @Luke Gavel,

What you have done will allow the server to start, but you will lose all functionality provided by the disabled plugins.

As @Tinker Fadoua pointed out, on your production environment you might want to click on the "JIRA update check" link at the bottom of the Manage Addons page.  This will allow you to select the version and it will give you a report of which installed addons are compatible, incompatible until you upgrade the addon, or incompatible with the new version.

If you don't need those plugins to be functional post upgrade then you should be fine with what you have done.  If however, some of your users are counting on that functionality you may want to look at having some of them test the upgrade and you make want to look to the plugin vendors to see when they will be providing updated versions of the plugins.

Just a couple of things to keep in mind.

I hope that helps!

-James

Tinker Fadoua · Answer

@Luke Gavel

You upgraded straight from v7.5.2 to v8.1.0? Without going through other versions?

Did you test before upgrade which plugins are incompatible?

Best,

Fadoua