Add policy for auto-assigning S1 bugs with SLOs of 30 days
What does this MR do and why?
This MR adds a policy which automatically updates un- or mis-scheduled S1 bugs, assigning a due date 30 days out and the corresponding milestone. S1 bugs that are already scheduled for an appropriate milestone are not affected.
Higher-urgency categories of S1 bugs (availability, security, and corrective actions) have tighter SLOs than the baseline S1 SLO and are not included in this iteration. They will be covered in a future iteration once this groundwork is laid.
Fulfills the baseline technical implementation for gitlab-org/gitlab#362985 (closed)
Closes https://gitlab.com/gitlab-com/quality/engineering-productivity/-/issues/6
Immediate impact
Of the 13 currently open S1 bugs that would be covered by this policy, 8 are assigned to either the current or next milestone (%15.0 or %15.1). If run today, this policy would only impact the remaining 5 bugs that are not scheduled for an appropriate milestone.
Ongoing impact
The number of S1 bugs opened over the past 6 months is as follows:
| Month | Total S1s | S1s covered by this policy |
|---|---|---|
| 2022-04 | 20 | 16 |
| 2022-03 | 17 | 14 |
| 2022-02 | 14 | 13 |
| 2022-01 | 12 | 11 |
| 2021-12 | 5 | 5 |
| 2021-11 | 9 | 9 |
On an ongoing basis, this shows that we can expect anywhere from ~5-20 S1s per month, on average, to be automatically scheduled per this policy.
Dry runs
Action items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group=> -
Relevant Slack channels => -
Engineering week-in-review
-