Design: Advanced filtering on vulnerability report
Release notes
Problem to solve
Users require more filters than we currently have in the vulnerability reports. We should thoughtfully expose all the data we have available and consider additional user-friendly data combinations to allow the users an enterprise filtering experience.
Intended users
User experience goal
Proposal
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Designs
Relates to
Activity
added to epic &3308
added typefeature label
mentioned in issue gitlab-org/quality/triage-reports#553 (closed)
changed milestone to %Backlog
added [deprecated] Accepting merge requests label
removed featureenhancement label
changed epic to &4812
mentioned in issue #267754 (closed)
mentioned in issue #267572 (closed)
marked this issue as related to #262079 (closed)
marked this issue as related to #267754 (closed)
mentioned in issue #342079 (closed)
Replaced by #342079 (closed). Closing.
Please register or sign in to reply