How to reset Bamboo plugins state through database

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

Summary

Disabling apparently unusable plugins may seem a good idea, but it can lead to bad consequences. Plugins have dependencies and when their dependences are not loaded they are not able to load themselves. This could be catastrophic in case you disable a system plugin. These plugins are usually root dependencies for many other plugins and it could affect main Bamboo features.

The following query will help you to identify if there are any plugins with state manually changed (not in their default state)

1 SELECT * FROM bandana WHERE bandana_key='bamboo.plugin.state';

In case there are add-ons manually disabled their state will be visible in the serialized_data column as observed in the following example:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 bandana_id | build_id | bandana_key | serialized_data ------------+----------+---------------------+------------------------------------------------------------------- 131113 | 0 | bamboo.plugin.state | <com.atlassian.plugin.manager.DefaultPluginPersistentState> + | | | <map class="java.util.Collections$UnmodifiableMap"> + | | | <m> + | | | <entry> + | | | <string>com.atlassian.analytics.analytics-client</string>+ | | | <boolean>false</boolean> + | | | </entry> + | | | <entry> + | | | <string>com.atlassian.streams</string> + | | | <boolean>false</boolean> + | | | </entry> + | | | </m> + | | | </map> + | | | </com.atlassian.plugin.manager.DefaultPluginPersistentState>

The above results show that both com.atlassian.analytics.analytics-client and com.atlassian.streams plugins are disabled.

Solution

  1. Stop Bamboo

  2. Backup your database to perform the next change

  3. Run the following query against Bamboo database:

    1 DELETE FROM bandana WHERE bandana_key='bamboo.plugin.state';
  4. Start Bamboo

Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.