- 
    New Feature 
- 
    Resolution: Fixed
- 
    Major 
- 
    None
While Jenkins automatically downloads dependencies of plugins, it doesn't tell you when you have configured an invalid plugin configuration by disabling plugins: Features simply don't work.
Ideas:
New Administrative Monitor:
- Tell users about mandatory plugin dependencies that are missing or disabled
- Tell user when implied (pre core extraction) dependencies are missing or disabled
Enhance plugin descriptions to state dependencies, maybe color-code when they're missing or disabled.
Show a confirmation dialog before disabling a plugin when a user clicks the check box.
- depends on
- 
                    JENKINS-31605 Plugin manager allows uninstalling bundled plugins -         
- Closed
 
-         
- is duplicated by
- 
                    JENKINS-30644 Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin -         
- Resolved
 
-         
- is related to
- 
                    JENKINS-21486 Refuse to load a plugin if dependencies are disabled or outdated -         
- Resolved
 
-         
- 
                    JENKINS-19859 Dynamic installation of plugin permitted even when dependencies must be updated first -         
- Open
 
-         
- 
                    JENKINS-19045 No page found 'digest.jelly' -         
- Resolved
 
-         
- 
                    JENKINS-22051 build.xml not created after successful build -         
- Resolved
 
-         
- 
                    JENKINS-21485 AdministrativeMonitor for plugins that have failed -         
- Resolved
 
-