Don't remove compliance frameworks when top level group is the same
What does this MR do and why?
What
- Updates project transfer service to only remove compliance frameworks if moved outside of top level group
Why
- Few bugs/reports of users moving their projects inside of a top level group and having their frameworks removed
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
No visual UI changes
How to set up and validate locally
- Create a sub-group under a top-level group
- Create a project inside the top-level group
- Create a compliance framework inside the group and attach it to the project https://docs.gitlab.com/ee/user/group/compliance_frameworks.html
- Transfer the project to the sub-group
- Check the project has the same compliance framework
Related to #444455 (closed)
Edited by Jay Montal