Issue Summary

The steps mentioned in the article Cannot enable or disable bundled system apps or modules do not permanently enable or disable the bundled system modules because the changes made via the SQL method or UPM API method are getting reset after every Confluence restart.

 Kindly note that the steps work perfectly fine for the entire plugin.

Steps to Reproduce

As an example, we have tested disabling the notification-templates-comment-remove-1.0.0 module using both methods below in the latest Confluence versions 8.1.1 and 7.20.2

UPM REST API method

• Run the below REST API command which disables the notification-templates-comment-remove-1.0.0 module
  module key: com.atlassian.confluence.plugins.confluence-email-resources-key
  plug-in key: notification-templates-comment-remove-1.0.0-key

  curl -H "Authorization: Bearer <token>" --location --request PUT 'https://<domain>/confluence/rest/plugins/1.0/com.atlassian.confluence.plugins.confluence-email-resources-key/modules/notification-templates-comment-remove-1.0.0-key' \
  --header 'Content-Type: application/vnd.atl.plugins.plugin.module+json' \
  --data-raw '{
      "enabled": false
  }'

• Check if the module got disabled. Go to Settings > Manage apps > Filter the App Confluence Email Notifications Plugin >> Expand the list of modules and verify if the module notification-templates-comment-remove-1.0.0 is disabled.
• Restart Confluence
• Verify if the module notification-templates-comment-remove-1.0.0 is enabled.

SQL method

• Check if there is an entry for the related module notification-templates-comment-remove-1.0.0

   select BANDANAVALUE from BANDANA where BANDANAKEY = 'plugin.manager.state.Map';

  It should display the result as below with either true/false.

  <entry>
      <string>com.atlassian.confluence.plugins.confluence-email-resources:notification-templates-comment-remove-1.0.0</string>
      <boolean>true</boolean>
    </entry>

• Modify the particular entry and set it as false. If you don't get any entry for this module then insert the below entry in the Bandana value.

  <entry>
      <string>com.atlassian.confluence.plugins.confluence-email-resources:notification-templates-comment-remove-1.0.0</string>
      <boolean>false</boolean>
    </entry>

• Run the below SQL to update the details.

  update BANDANA 
  set BANDANAVALUE = '<full_string_from_above_step>'
  where BANDANAKEY = 'plugin.manager.state.Map';
  

• Check if the module got disabled. Go to Settings > Manage apps > Filter the App Confluence Email Notifications Plugin >> Expand the list of modules and verify if the module notification-templates-comment-remove-1.0.0 is disabled.
• Restart Confluence
• Verify if the module notification-templates-comment-remove-1.0.0 is enabled.

Expected Results

The module notification-templates-comment-remove-1.0.0 must be always disabled after Confluence restart unless we change it again via SQL or UPM API methods.

Actual Results

The module notification-templates-comment-remove-1.0.0 settings are getting reset after the Confluence restart.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.