Delay All Schema Updates and Trigger it at The Same Time

Due to how Confluence is build, schema updates can happen any time when the instance is up and running especially for plugins, including third party plugins operation.

This made specific database configuration where Confluence can only use regular account that unable to updates database schema not possible.

In order to workaround this, Confluence should provide a feature that could delay all schema updates and trigger at the same time when the administrator prefer.

In regards to plugin installation process, Confluence could mark this plugin as inactive until all the necessary process to complete its installation are triggered at the same time as the other schema updates process.

Possible Implementation

A new queue menu under JIRA administrators could be implemented for this feature. Like Mail Queue menu, administrators have the privilege to see the pending task that need to be run and administrator can choose which task to run individually or the whole queue at the same time