Compliance Framework labels removed when project is moved.
Summary
customer reported that a when moving a project within groups in the same parent group the Compliance Framework gets removed from the project. This creates a compliance risk
Base on slack discussion this seems related to #396281 (closed)
Steps to reproduce
Initial state:
PARENT Group (<-- where we apply the Compliance Framework)
-- sub-group A
-- sub-group B
---- project foo
In this setup, the compliance framework is applied everywhere above.
Now we move the project "foo" to another group:
PARENT Group (<-- where we apply the Compliance Framework)
-- sub-group A
-- sub-group B
---- sub-sub-group B1 (<-- new sub-group)
------ project foo (<-- moved to the new sub-group)
Example Project
What is the current bug behavior?
Compliance framework (labels) are removed from project when moved
What is the expected correct behavior?
Compliance framework (labels) should be maintained when the projects is moved within the same Top level group.
Relevant logs and/or screenshots
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)