Check that scheduled issues have a team label
It happened. We missed ad issue because of a missing team label.
Fortunately, it was manually spotted in time, and it was not a big one, so it was immediately addressed and so there are no problems. But this makes me think it could happen again, next time maybe with potential critical impacts.
The problem was on issue https://gitlab.com/gitlab-org/gitlab-ce/issues/45557, that had no team label assigned. So, even if discussed and scheduled for %11.0 beforehand, it was lost during planning sessions because it didn't show up in the issue boards.
Probably a good way to avoid this kind of problems in the future is to check with gitlab-triage
rules if all issues scheduled with a milestone (or maybe just with the current/next milestone) have a team label. If not, ping @gl-product
to ensure that this is an intended exception. I don't see any case where an issue in gitlab-ce
or gitlab-ee
repos shouldn't have a team label at all, so it should not create false positives.