Bot should remind team members to add missing group:: label to infradev issues
Summary
Issues with the infradev label carry an SLO to ensure we stay responsive to infrastructure availability needs. Infradev issues without a ~group:: label are at risk of falling through the cracks and missing their SLO due date, since it is unclear which group engineering manager should triage and prioritize them. This issue proposes having the gitlab bot remind team members to add a group:: label to any infradev issue that lacks one.
Proposal
For any issue with the infradev label and no ~group:: label the bot should add a comment reminding team members that a group:: label should be added.
Example
The issue Metrics for login attempts and status (gitlab-org/gitlab#385011 - closed) was initially assigned to an incorrect group. When that group label was removed the issue wasn't reviewed again until it was already overdue. Having the bot remind team members in this case would likely have resulted in the issue being prioritized before it breached SLO