WIP: TMP backend for "Security Reports provide permissions instead of paths for Vulnerability feedback"
requested to merge 9286-use_vulnerability_feedback_paths_for_permissions into 9412-split_vulnerability_feedback_permissions
What does this MR do?
Apply new Feedback permissions to MR, Pipeline view and Project level dashboard.
WIP: This is a temporary MR until https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9700 get's merged
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
EE specific content should be in the top level /eefolder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan? -
Security reports checked/validated by reviewer
Refs #9286 (closed)
Edited by Olivier Gonzalez