Moving a project to a new root group breaks the milestone selection for new merge requests

This bug is reproducible

Bug behavior

  • We moved a project from one root group to a subgroup in another root group. Both root groups define milestones.
  • After the move, when we open an new MR, the "New merge request" dialog offers milestones from the old (moved from) group but not the milestones form the new (moved to) group:
    New_merge_request___Cobai__Online_sales_platform__core___GitLab_2022-06-28_at_18.15.18
  • After creating the MR, the MR sidebar offers the new (correct) milestones:
    Downgrade_kotlin_version__203____Merge_requests___Cobai__Online_sales_platform__core___GitLab_2022-06-28_at_18.15.53

Expected behavior

When creating a new MR, the milestone drop down should only show milestones from the new group, not from the old (migrated from) group.

Further findings

Moving the project to a new subgroup in a different parent group has recreated all milestones from the old parent group as project milestones in the moved project - that looks ok. All newly created milestones have been expired (that's right) and open (that's wrong, we closed all milestones before the move). Still, the "new MR" dialog showed only the old (recreated) milestones - i just double checked. I've now closed all milestones created by the move and only now do i see the new milestones that exist in the target group. So, it's technically fixed now, but something is rather botched.

Edited by Dirk Lachowski