Promoting a project milestone to a group one had as a result to assign that milestone to a bunch of issues/MRs.
As the title says, promoting a project milestone to a group one had as a result to assign that milestone to a bunch of issues/MRs.
@MadLittleMods wrote (chat link ) that recently he promoted the 10.4 milestone from https://gitlab.com/gitlab-com/customers-gitlab-com/milestones/7 to a group milestone https://gitlab.com/groups/gitlab-com/-/milestones/6.
I think it's related, and that caused a lot of issues/MRs under the gitlab-com
namespace to get assigned to this milestone. Strangely enough, there's no system note in any of those, it just happened behind the scenes.
Useful links
- 4 years ago MRs with a recent 10.4 milestone: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests?milestone_title=10.4&page=373&scope=all&state=all, that can't be right
- Issue opened by a guest user, got the 10.4 milestone added to it although non-members do not have access to do this: https://gitlab.com/gitlab-com/gitlab-docs/issues/143 (you can see in the system note I removed it)
Steps to reproduce
I'm not really sure, we've promoted other milestones in the past, but maybe a conflict of their iids caused this? I'm not really sure.