[JENKINS-60117] Rework sorting for the Enabled columns of Installed in Plugin Manager · jenkinsci/jenkins#20694

2019-11-10T10:27:30.000Z

This is detached from JENKINS-59665 by jsoref open /pluginManager/installed (Jenkins 2.198) Have: a couple of plugins with dependencies (enabled) a couple of plugins (disabled) a couple of plugins that have never been upgraded a couple of plugins which have been upgraded Actual results I can't really explain what it's doing. – It appears to be stable (i.e. toggling the sort direction for one of these columns reverses the sort), but it isn't global (i.e. changing the sort key to a different column, e.g. Name, and then back to the Enabled column results in a new sort). Expected results Sorting by Enabled should sort into three sets: Enabled (checkbox checked) Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) Disabled (checkbox unchecked) --- Originally reported by oleg_nenashev , imported from: Rework sorting for the Enabled columns of Installed in Plugin Manager assignee : kalana status : Open priority : Minor component(s) : core label(s) : newbie-friendly, plugin-manager, ux resolution : Unresolved votes : 0 watchers : 5 imported : 2025-11-24 Raw content of original issue This is detached from JENKINS-59665 by jsoref open /pluginManager/installed (Jenkins 2.198) Have: a couple of plugins with dependencies (enabled) a couple of plugins (disabled) a couple of plugins that have never been upgraded a couple of plugins which have been upgraded Actual results I can't really explain what it's doing. – It appears to be stable (i.e. toggling the sort direction for one of these columns reverses the sort), but it isn't global (i.e. changing the sort key to a different column, e.g. Name, and then back to the Enabled column results in a new sort). Expected results Sorting by Enabled should sort into three sets: Enabled (checkbox checked) Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) Disabled (checkbox unchecked) 1 attachment - [jenkins.jpg](https://raw.githubusercontent.com/jenkinsci/attachments-from-jira-issues-core-cli/refs/heads/main/attachments/49777/jenkins.jpg) > ![jenkins.jpg](https://raw.githubusercontent.com/jenkinsci/attachments-from-jira-issues-core-cli/refs/heads/main/attachments/49777/jenkins.jpg)

(10 comments) (0 reactions) (0 assignees)Java (25,266 stars) (9,474 forks)batch import

component:coreenhancementgood first issueimported-jira-issueplugin-managerpriority:minorresolution:unresolvedux

Description

jenkins.jpg

Contributor guide

Tech stack: javajavascript
Domain: frontend
Issue type: feature
Difficulty: 3
Estimated time: half day
Activity status: stale
Clarity: clear
Prerequisites: Java programmingBasic Jenkins plugin manager UI knowledge
Newbie friendliness: 75
Research direction: Investigate the current sorting implementation for the Enabled column in the Plugin Manager's Installed tab. Check the Jelly view files (e.g., PluginManager/index.jelly) and any associated JavaScript sorting logic. The expected behavior is to sort into three groups: enabled, enabled but cannot be disabled, and disabled. Focus on modifying the comparator to achieve this three tier sort. Refer to the attached screenshot for the existing UI. Look for any prior discussion in the issue comments (10 comments) for hints on the approach.