Bug KPI follow up and polish
Per feedback from the last key review -- https://docs.google.com/document/d/11eLscbiPvHKlBxEB4PbRqOrlMt2lJ_NiMCVuNJivE-E/edit#bookmark=id.i2rksoq5wf8u
Craig: I am arguing that the chart should be pivoted on close date so there is no bias in the data. If you look at the current month it will look better. Sid: Yes, it should be open date not closed date. Kyle : The time series is when the bug is open.
Sid: This is a tough one similar to sales. Should it be closed out or not so it shows a %. Craig: can also use resolved within a certain period of time (ex. 30 days) Sid: That sounds great to me. Craig: Stick with open dates. Instead of ave. Closed time by percentages closed by time. Sid: look at support’s approach with SLA achievement
Tasks
-
Rename to MTTC -- Mean Time to Close -
Investigate if pivoting to closed date would tell a different story -
Make decision/confirm the approach of open/close date -
Instead of average, do closed time by percentages. How many are under how many are over.
Proposal for closed within SLO
- Combined percent closed line chart for all serverities: https://app.periscopedata.com/app/gitlab/576726/GitLab-Bugs?widget=10471849&udv=913732
- Separate SLO charts for Severity 1 and Severity 2:
Edited by Kyle Wiebers