Security Reports provide permissions instead of paths for Vulnerability feedback
Currently the security reports provide a boolean additionally to the Vulnerability:
We already have it changed for the Security Dashboard (https://gitlab.com/gitlab-org/gitlab-ee/issues/8150) to the model of only providing the paths when the current user has the actual permissions.
In order to align this, we should do the same. This also helps us in the Frontend, because we do not have two distinct ways we have to handle.
Tasks
-
backend
-
Expose the paths ( vulnerability_feedback_dismissal_path
andvulnerability_feedback_issue_path
) instead of permissions -
Pipelines View should use can?
instead ofshow_new_issue_link?
, so that this is consistent with all the other places
-
-
frontend
-
Use the new paths instead of the permissions to determine when to show the action buttons
-
Edited by Lukas Eipert