GraphQL Vulnerabilities filter by activity
In order to support #230381 (closed), the current vulnerabilities
GraphQL query needs to support filtering by issueLink.state
.
Implementation Plan
-
extend Resolvers::VulnerabilitiesResolver
to support 2 new arguments:-
has_resolution
- it will filter vulnerabilities by value ofresolved_on_default_branch
field (it would be great to have #227114 (closed) implemented first, it will simplify the query), -
has_issues
- it will filter vulnerabilities by existence of IssueLink (no need to filter byissueLink.state
I think, we might need to clarify ifhas_issues
filter should filter CREATED issues or should also include RELATED issues)
-
-
extend Security::VulnerabilitiesFinder
to support filtering byresolved_on_default_branch
andissue_link_states
, -
extend Vulnerability
model with scopes to allow filtering byresolved_on_default_branch
andissue_link_states
Edited by Alan (Maciej) Paruszewski