Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Possibility to filter vulnerabilities on Score and Severity field #640

Closed
rguignard opened this issue Apr 22, 2020 · 0 comments
Closed

Possibility to filter vulnerabilities on Score and Severity field #640

rguignard opened this issue Apr 22, 2020 · 0 comments
Assignees
@SamuelHassine
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 3.3.0

Comments

@rguignard
Copy link

Problem to Solve

As you have introduced the notion of score and severity on a vulnerabily in your model, it could be usefull to be able to filter vulnerabilities on this field.
Also, a filtering option on the creation date could also be usefull

Current Workaround

Proposed Solution

Additional Information
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Apr 22, 2020
@SamuelHassine SamuelHassine self-assigned this Apr 22, 2020
@SamuelHassine SamuelHassine added this to the Release 3.1.2 milestone Apr 22, 2020
SamuelHassine pushed a commit that referenced this issue May 26, 2020
[api/frontend] Add more filters to vulnerabilities list (#640)
ff506ba
SamuelHassine pushed a commit that referenced this issue May 26, 2020
[api/frontend] Add more filters to vulnerabilities list (#640)
bdd34b4
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 3.3.0
Development

No branches or pull requests
2 participants
@SamuelHassine @rguignard