Imported milestones do not observe duplicate milestone title rules
All milestones within a root_namespace, whether group or project milestones, must have unique titles. This is intentional, to reduce confusion.
In the UI, when a user attempts to create a milestone with an existing title, they will see an error message and the milestone will not be created:
However, when importing a group via file-based import, existing group milestones with duplicate names have their group_id updated to the new destination resource id, thereby "moving" from their original group to the newly imported group.
Validation steps
- Create a group, create a milestone for the group titled e.g. "17.0", create a subgroup, create a milestone for the subgroup titled e.g. "18.0", create a project in the subgroup, create a milestone for the project titled e.g "19.0"
- Open each milestones list page for the group, subgroup, and project for later reference.
- Export the group `settings > general > advanced > export group
- Once ready, download the export file
- Navigate to the group home page
- Create a new subgroup
- Select the "You can also import an existing group." option neat the top of the form
- Import the group with the "Import group from file" option, using the downloaded export file
- Once the import finishes, visit the milestones list page for the group, subgroup, and project and refresh each page.
- Observe the milestones for the group and subgroup are no longer visible.
- Visit the corresponding imported group and imported subgroup milestone list pages
- Observe the milestones now appear on these pages
Edited by Carla Drago
