Default Compliance framework set at sub-group being applied at top level group
Summary
Settings (Compliance framework) configured within on group appear to be affecting other groups.
Steps to reproduce
Configure a default Compliance framework from on a sub-group; observe as new projects created at the top level group have the Compliance framework applied.
What is the current bug behavior?
At attempt was made to configure a default compliance framework at a subgroup level; it was later found that any new project created at the top level group had the framework applied as well;
The following diagram illustrates the group hierarchy in question:
What is the expected correct behavior?
The settings (screenshot following) imply that all changes made to Tanuki Financial should only pertain to Tanuki Financial but this was not the case in this scenario (it was applied to GitLab Learn Labs level):
Expected behavior was for the configuration of the Compliance framework to only pertain to the context of the particular group in question (Tanuki Financial).
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)
Possible fixes
Remove the ability to set default framework functionality from subgroups