FY22-Q1 Create: Source Code BE KR: Improve quality SLOs for S1s and S2s by 40% => 33%
In the past year we have seen a steady increase in backlog bugs for both Source Code and Code Insights. As key parts of our product we would like to see our Sev1 and Sev2 bugs under a more SLA based solution. In this quarter we would like to see improved SLOs.
The target improvements is an 40%, aggregated across all measures.
Metrics being analyzed:
- https://about.gitlab.com/handbook/engineering/development/performance-indicators/dev/create/#source-code-group-quality-indicators
- https://about.gitlab.com/handbook/engineering/development/performance-indicators/ops/verify/#continuous-integration-group-quality-indicators
It's important to note that while SLOS are showing Mean Time to Resolve being below target, our open bug count is going up. We think this may be that once bugs are triaged they are either fixed or ignored from a priority consideration.
Steps to address this may include
-
Make sure data is correct for these groups and update to reflect proper information -
Consider changing MTTR to be (open bug age + closed bug aged)/(# open bugs + # closed bugs) -
Review current open bugs for how long they were open -
Work with product to demonstrate this problem and get bugs prioritized to bring down so that open bugs more closely matches a months worth of opened bugs
List of open groupsource code backend "Missed SLO" issues:
Edited by Sean Carroll