Triage workshop for EMs and PMs with published recording
Summary
This work is part of our initiative to reduce the time to resolve bugs overall. https://quality-dashboard.gitlap.com/groups/gitlab-org/time_to_close_bugs
Google doc: https://docs.google.com/document/d/1E6TJecciYlJJzgEMNCUuk494K3cywjIOLqPhOHQeWbc/edit#
Content
- Run through our new triage package V2.0 triage-ops#186
- Show the new 5x5 heat map on open bugs for each group triage-ops#166
| ~S1 | ~S2 | ~S3 | ~S4 | no severity |
|
|---|---|---|---|---|---|
| ~P1 | 2 | 0 | 0 | 0 | 1 |
| ~P2 | 0 | 2 | 8 | 1 | 1 |
| ~P3 | 0 | 0 | 7 | 1 | 3 |
| ~P4 | 0 | 0 | 2 | 7 | 1 |
no priority |
1 | 6 | 19 | 5 | 145 |
- Show the missed-SLO detection mechanism and the visualization triage-ops#137
- Go over the latest revision of severity and priority labels https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29694
- Go over triage levels https://about.gitlab.com/handbook/engineering/issue-triage/#triage-levels
Episodes
Episode 1 - 2019-07-01
- Introduction to triage operations https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations
- Challenges, ~400 new issues in CE and EE every week.
- Important triage packages
- Initial triage of new issues https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#newly-created-unlabelled-issues-requiring-initial-triage
- Complete triage, done by engineering PM and EMs. https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#stage-level-issues
- Examples
- Revisit priority and severity definitions
- Triage package V2.0
Recording: https://www.youtube.com/watch?v=qOlN2G1BDhk&feature=youtu.be