-
Bug
-
Resolution: Fixed
-
Major
-
-
2.344
I've updated to 2.332.2 (from 2.303.2) and I'm not able to disable the Jira plugin anymore.
If I hover the mouse over the toggle, it tells me it cannot be disabled because it is used by the "Jira integration for Blue Ocean"
I disable it, restart jenkins and still the toggle switch for the Jira plugin is disabled. If I hover over it there is no warning box either.
The workaround is to open the developer console and remove the class "has-dependents" to enable the toggle.
- causes
-
JENKINS-69347 Can enable a plugin with disabled dependencies (regression in 2.344)
-
- Open
-
- is caused by
-
JENKINS-68285 Modernise the appearance of the plugin manager
-
- Resolved
-
dcendents When filing regression bugs, it is helpful to include the steps to reproduce, expected results, and actual results as described in the Issue Reporting documentation. As a courtesy, I have taken the liberty of providing this information below:
Steps to reproduce
Expected results
Note: These are the actual results prior to 2.325.
Jira can be disabled, because Jira Integration for Blue Ocean was disabled previously.
Actual results
Jira cannot be disabled. The enabled slider is grayed out. Hovering over the ⓧ on the right hand side, the UI says (erroneously!): "This plugin cannot be uninstalled. It has one or more installed dependencts. Jira Integration for Blue Ocean"
Evaluation
Bisection reveals this regression was introduced in 2.325 in jenkinsci/jenkins#5916 (
JENKINS-68285).