GraphQL errors with partial data on the vulnerability report should indicate which vulnerability is causing the problem
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Why are we doing this work
With !165675 (merged) we started allowing the vulnerability report to handle graphql errors with partial data. It is difficult for customers to resolve these errors because the error messages don't indicate which vulnerabilities are causing the problem.
Proposal
Use the path parameter in the error to find the vulnerability which is causing the issue.
Display a link to this vulnerability alongside the error message.
Relevant links
- Stop requesting data from Jira when rendering t... (#497199)
- https://gitlab.com/gitlab-com/sec-sub-department/section-sec-request-for-help/-/issues/374+
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
Verification steps
Edited by 🤖 GitLab Bot 🤖
