Improve representation of urgent customer bugs
This was a ~Severity::2 customer bug that was a significant blocker for a single large customer.
Besides team-members working on the bug it was difficult to convey urgency for the bug and prioritize reviews.
Proposal
This issue is to discuss possible ways to better represent high-priority bugs for important customers. It may result in a handbook update. Possibilities to discuss include:
- Improve criteria for S1 such that this bug would be S1 next time
- Review Incident guidelines and consider whether an incident might have been appropriate