Skip to content

Add Top-level group transfer limitations

Jefferson Jones requested to merge docs-migrating-groups-saas-limitations into master

What does this MR do?

Would like to add learnings to documentation, see below:

I faced a situation with a customer that were attempting to transfer a top level namespace (gitlab.com/example) with a subscription applied as they would like to migrate (direct transfer) into their other primary top level namespace (gitlab.com/home), however we have prevented this transfer when a subscription has been applied: per MR: !65689 (diffs)

Top level namespaces cannot be directly transferred as subgroups into other top level namespaces on SaaS when a subscription has been applied.

So I then spent a great deal of time trying to identify the product team and understand a viable path for the customer: Please see the technical report I shared: https://gitlab.slack.com/archives/C02PVELLMJ7/p1668535383233379?thread_ts=1668535369.741089&cid=C02PVELLMJ7

I then performed MVC testing a Transfer, by first removing a subscription. transferring to the other namespace and reapplying the subscription and had success, but still would like Product confirmation before suggesting this workaround as a viable path to customers, as I have concern around data loss or items not transferring correctly/completely: https://gitlab.slack.com/archives/C02AZ7C32N5/p1669821297223099?thread_ts=1668181020.212749&cid=C02AZ7C32N5

Related issues

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Jefferson Jones

Merge request reports