While upgrading the Configuration Manager for Jira (CMJ) app, the Atlassian UPM disables and enables Atlassian packages causing downtime to DC instances. Configuration manager has dependent plugins which are stopped during the upgrade. But UPM disables all the dependent apps.
Explanation
Due to its integration with Configuration Manager for Jira (CMJ), the Insight app imports com.botronsoft.cmj.spi.* dynamically from the CMJ SPI (Service Provider Interface) bundle. Thus, the Insight app gets restarted upon uninstalling/disabling CMJ. Moreover, all core system plugins that depend on Insight app are restarted due to its restart causing problems in using core system functionalities as a result.
...
As of Jira 8.19.0 onwards, disabling/uninstalling the Configuration Manager Core bundle (installed with Configuration Manager for Jira app v. 6.10.5 and previous versions)
or
Disabling/uninstalling Configuration Manager for Jira SPI Bundle ( installed with
Configuration Manager for Jira up to v. 6.10.6) results in the largely increased number of dependent plugins to be disabled and re-enabled.
Expected Results
When uninstalling/disabling a given app (root plugin), the list of dependent app to be disabled/re-enabled is limited to those that require the root plugin.
Actual Results
When uninstalling/disabling a given app (root app), the list of dependent plugins to be disabled/re-enabled includes also many transient dependencies that do not require the root plugin.
Workaround
Dependent plugins, have to be enabled manually from Jira’s "Manage Apps".