[Custom Fields] Handle moving of namespaces

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

When a root-level namespace containing custom field settings is moved under another namespace, we should decide on what to do with the existing configuration.

We can leave them as-is so that they become active again in case this was a mistake and the namespace becomes a root-level one again.

Or we can clean up the existing data.

Edited Jul 31, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading