Design: Post-MVC: Advanced filtering & search on the Vulnerability Report
Overview
This is the follow-up iteration to Design: MVC: Advanced filtering & search on the Vulnerability Report.
This issue explores UX/ UI elements we determined were out of scope for the MVC. These are:
- Users can search with raw text/ keyword
- 'HTTP' in description, fuzzy-text search
- Filter by Identifier
-
Identifier = CVE-2023
prefix match only
-
- Filter by Location (folder or file)
Post-MVC under consideration:
- Detected Date
- Cluster (operational vulnerabilities)
- Image (operational vulnerabilities)
- Separating out the
Tool
filter into analyzer and scanner separately- There's also a request to separate out the DAST API filter here
Questions
- How is the filtered search component going? If introducing it in the MVC generated any serious usability concerns, we could go back to considering a custom filter component and separating out search when it's performant.
Persona
Business objective:
- Increase user satisfaction with Vulnerability Management features
- Increase adoption of Ultimate by improving the Vulnerability Report experience (only available to Ultimate customers)
- Develop and share components in order to improve customization and usability on all tables across GitLab product
Edited by Becka Lippert