Move issue to next milestone after its due date
Problem
TODO
Old description
gitlab-bot
moves issues to the next milestone if they missed the current one, and adds a bunch of labels. But since the release schedule has changed, it doesn't run at release time, but a lot later -- leaving issues stuck in their old milestone for weeks. In turn, this breaks our dashboards used for picking up new work, as well as messing up milestone planning.
(I'm asking for the gitlab-org/gitaly
project in particular but this is probably relevant for others, too)
Looks like this runs from https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/pipeline-schedules.yml#L234-264 (?).
Ideally (for my dashboards anyway), this would run right at the same time as %Upcoming
changes.
From Slack:
We might want to use https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/releases.yml?ref_type=heads as a SSOT for scheduling.
https://gitlab.slack.com/archives/CCFV016SV/p1707826810645999
Proposed solution
Let triage-ops
move milestones in issues/merge request right after milestone due date.