I was doing some MR triaging and noticed a few MRs that were not being picked up by the "Inactive community MRs" script because the GitLab bot was updating the milestone every month which counted as an activity :sweat_smile: One of these stayed open for over a year due to this. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24359 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55691 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57977 ### Proposal There are three possible proposals I can think of. I've listed them below in order of decreasing complexity and usefulness. 1. We find a way to ignore the moving milestone and application of the missed milestone label when determining inactivity. 2. We stop the bot from auto moving the milestone on triage-reports~2091545 MRs 3. We make it policy not to have release milestones on triage-reports~2091545 MRs