Detect bugs that surpassed the SLOs for their priority label
(Surfacing of stale, prioritised bugs)
Proposal
We can start with a summary report in one issue that we can show scorecards of time to resolve bugs for each team.
- Metric: SLA on ~P1 ~P2 ~P3 ~P4 depending on their tiers for customer customer+ ~bug or ~performance issue.
- What it tells us: Are teams executing well and scheduling things correctly.
- Anti-metric: Average time to resolve ~S1 ~S2 for customer customer+ ~bug or ~performance issue
- What it tells us: Are we actually delivering value to customers in a timely manner.
Metric
Metric: SLA on ~P1 ~P2 ~P3 ~P4 depending on their tiers for customer customer+ ~bug or ~performance issue.
- What it tells us: Are teams executing well and scheduling things correctly.
Average time to resolve ~bug and ~performance with customer or customer+ What it tells us: Are teams executing well and scheduling things correctly.
| Priority label | Threshold |
|---|---|
| ~P1 | more than 30 days
|
| ~P2 | more than 60 days
|
| ~P3 | more than 90 days
|
| ~P4 | Not implementing in this iteration |
Anti-metric
Anti-metric: Average time to resolve ~S1 ~S2 for customer customer+ ~bug or ~performance issue
- What it tells us: Are we actually delivering value to customers in a timely manner.
Implementation
There are recommendations for how long a bug should stay around based on it's priority label:
If these time windows are exceeded, detect and surface a report. Use ~"missed-SLA"
Ideas:
- Add to the group triage package
- Indexes bugs out of the priority window for each team
- Create a separate triage package
- Lists all of these bugs in one place
- Add a label via a triage policy and don't index in a package