Page Comparison

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 need to be 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 Plugin app imports dynamically com.botronsoft.cmj.spi.* dynamically from the CMJ SPI -Bundle(Service Provider Interface) bundle. Thus, the Insight Plugin app gets restarted upon uninstalling/disabling CMJ. Moreover, all core system plugins that depend on Insight Plugin app are restarted due to the its restart of Insight Plugin causing problems in using core system functionalities as a result.

It is likely that more people users will experience this that issue when they are on Jira 8.19 and/or with JSM 4.19 or above. It is identified that the problem seems to be caused by the integration of Insight with CMJ via the SPI.

As of Jira 8.19.0 onward onwards, disabling/uninstalling the Configuration Manager Core Bundle bundle (installed with Configuration Manager for Jira app v. 6.10.5 and previous versions)
or
disablingDisabling/uninstalling Configuration Manager for Jira SPI Bundle ( installed with
Configuration Manager for Jira up to v. 6.10.6) . Results results in the largely increased number of dependent plugins to be disabled /and re-enabled.

Expected Results

When uninstalling/disabling a given plugin app (root plugin), the list of dependent plugins app to be disabled/re-enabled is limited to those that require the root plugin.

Actual Results

When uninstalling/disabling a given plugin app (root pluginapp), 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".