Vulnerability Management Policy not respecting scope that references Compliance Framework
Summary
Customer has created a Vulnerability Management Policy and set the Policy Scope to Apply this policy to "projects with compliance frameworks" named "REDACTED" They then find this policy enabled in policies that do not have the "REDACTED" compliance framework in force.
In contrast, they showed a Merge Request Approval Policy similarly scoped that respects the Compliance Framework of the scope
US Gov ticket.
Steps to reproduce
Example Project
What is the current bug behavior?
Vulnerability Management policy is enabled on projects that are not in the configured scope
What is the expected correct behavior?
Vulnerability Management policies should only enable inside the configured scope.
Relevant logs and/or screenshots
Screenshots are in the linked ticket, currently.
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)