Refactor the team reports to make them more digestable
Extracted from https://gitlab.com/gitlab-org/quality/engineering-productivity/team/-/issues/370#note_1738817361.
If we're looking to adjust these triage reports (to include typemaintenance which I think is a good idea) we should consider refactoring the report to make it more digestable.
There are a couple of ways to pivot the data that could actually be easier for teams to consume but I'd want to chat with the teams to see what their needs are. I can give examples if we need to but I think one of the key ways we could think about this report differently is by grouping issues by their SLA.
What that means is, for items deliverable ASAP (S1 security, availability, and so on) we could have them in the same table. Basically we'd be grouping by SLA. Another alternative would be to group by severity label. It could look something like this:
severity1 deliverable immediately (SLA =< 4 hours)
bugvulnerability | bugavailability | typebug | SLOMissed | |
---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 |
priority2 | 0 | 0 | 0 | 0 |
priority3 | 0 | 0 | 1 | 0 |
priority4 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 0 | 0 |