/
Disabling/upgrading CMJ causes other apps to get disabled
Disabling/upgrading CMJ causes other apps to get disabled
In Jira 8.19+ it's observed that disabling Configuration Manager for Jira, and more specifically the CMJ SPI-Bundle app (part of the CMJ package), causes other system or third party apps to get disabled. This usually happens in the upgrade process of the app and all apps are automatically re-enabled afterwards. However, in a few cases the process takes too long and some apps are left disabled and require manual re-enabling.
This problem has been linked to recent changes in the way Jira's Universal Plugin Manager works and the coupling of Insight asset management with Jira Service Management.
There is an open bug which provides more details about the issue here - https://jira.atlassian.com/browse/JRASERVER-73869
, multiple selections available,
Related content
Configuration Manager for Jira - Snapshot cannot be deployed because of a disabled plugin
Configuration Manager for Jira - Snapshot cannot be deployed because of a disabled plugin
More like this
Issues when installing or upgrading plugins
Issues when installing or upgrading plugins
More like this
App Integrations
App Integrations
More like this
Release notes 6.15.2
Release notes 6.15.2
More like this
Connector for Salesforce & Jira not working when Requirements & Test Management for Jira is installed
Connector for Salesforce & Jira not working when Requirements & Test Management for Jira is installed
More like this