Skip to content

Keep compliance frameworks for project transfers

Jay Montal requested to merge 444455_add_root_ancestor_to_fix into master

What does this MR do and why?

What

  • Updates project transfer service to only remove compliance frameworks if moved outside of top level group (including subgroups in this MR fix)

Why

  • Few bugs/reports of users moving their projects inside of a top level group and having their frameworks removed, fix was deployed but nested sub groups still were affected since root_ancestor was missing

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

  1. Create a sub-group under a top-level group
  2. Create a project inside the top-level group
  3. Create a compliance framework inside the group and attach it to the project https://docs.gitlab.com/ee/user/group/compliance_frameworks.html
  4. Transfer the project to the sub-group
  5. Check the project has the same compliance framework /assign me

Merge request reports