Logical Stacking/Grouping of Patch Versions
Feature Request: Patch Management Improvements
1. Logical Stacking / Grouping of Patch Versions
Issue:
Patch Management currently displays multiple versions of the same patch as separate items, leading to:
- A cluttered list
- Difficulty identifying the latest relevant version
- Confusing or inaccurate reporting
- Inefficient patch evaluation workflows
Requested Enhancement:
- Introduce logic to group or stack all versions of the same patch under a single collapsed entry.
- Display only the latest applicable version by default.
- Allow users to optionally expand to see historical versions if needed.
2. Ability to Hide or Filter Out Specific Patches
Issue:
Customers cannot hide outdated or irrelevant patch versions, resulting in:
- Noise in the patch list
- False perception of devices being out of compliance
- Manual work to track what’s relevant
Requested Enhancement:
- Allow users to hide selected patches or categories of patches from visibility.
- Option to mark a device "up to date" regardless of deprecated patch entries.
3. Bulk Exclusion of Patches (Keyword-Based or Multi-Select)
Issue:
Excluding patches must be done one version at a time, which is extremely time-consuming—especially for vendors like Intel, Dell, or HP where dozens of minor revisions appear simultaneously.
Requested Enhancement:
Provide multiple bulk-exclusion options:
- Keyword-based exclusion (e.g., exclude all patches containing “Intel Extension”, “Dell Firmware”, etc.).
- Multi-select UI (checkboxes) to exclude many patches at once.
- Bulk actions (exclude, hide, group, etc.) for selected patches.
4. Improved Patch Display Customization
Issue:
Customers want more control over which patch categories or vendors appear, so only relevant updates surface.
Requested Enhancement:
- Allow filtering or toggling by vendor, patch type, severity, or category.
- Offer a simplified “clean view” showing only meaningful, actionable patches.
5. Enhanced Reporting Accuracy
Issue:
Reporting is skewed by the presence of older patch versions being listed as "missing," even when newer superseding patches exist.
Requested Enhancement:
- Update reporting logic to reflect supersedence and the latest required version.
- Ensure that hidden/excluded versions no longer impact compliance scores.
6. Roadmap Visibility for Patch Management Improvements
Issue:
Customer is in renewal evaluation and expressed frustration; they need clarity about whether patch usability improvements are planned.
Requested Enhancement:
- Provide a public or semi-public roadmap note indicating upcoming Patch Management enhancements.
- Offer improved internal communication on how these FRs progress through Product review.