The Gadget Dashboard bundled plugin is not available error when accesing JIRA applications
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The user logs in JIRA applications: suddenly an error exception is thrown on the screen. It says that the Gadget Dashboard plugin (the one responsible for load that user dashboard) is not available. Although you be able to see this plugin really disabled on administration section, it cannot be re-enabled because a non-specified web fragment is also disabled.
The following error is thrown in the screen:
1
2
3
4
5
ERROR
The Gadget Dashboard bundled plugin is not available. Please contact an administrator to ensure the Gadget Dashboard plugin is enabled!
Perhaps you need to log in to see the page.
If you think this message is wrong, please consult your administrators about getting the necessary permissions.
Or during the end of the installation error below occurred:
1
2
3
Error
Error
The Gadget Dashboard bundled plugin is not available. To ensure the Gadget Dashboard plugin is enabled, please contact your JIRA applications administrators.
Cause
The Gadget Dashboard is a bundled plugin of a JIRA application and should always be enabled. The conditions in which this won't occur:
The plugin has been disabled.
The plugins timed out on startup.
Resolution
Access the Add-on Manager and verify the plugin is not disabled. This can also be done from the database as in Jira Data Center startup fails with a message that required plugins are not started.
Run through the steps in Bundled plugin not available error thrown on Jira server login.
Was this helpful?