How to Judge Severity / 如何判断严重等级
Decision Framework / 判定框架
When assessing bug severity, ask yourself these questions in order:
判定 Bug 严重等级时，按顺序问自己以下问题：Key Factors / 关键因素
1. User Impact / 用户影响
- How many users are affected? / 影响多少用户？
- Is this on a critical path? / 是否在关键路径上？
- Can users complete their goal? / 用户是否能完成目标？
2. Business Impact / 业务影响
- Does it affect revenue? / 是否影响收入？
- Does it affect brand reputation? / 是否影响品牌声誉？
- Is it in a compliance-critical area? / 是否涉及合规关键领域？
3. Workaround / 变通方案
- Is there a workaround? / 是否存在变通方案？
- How complex is the workaround? / 变通方案有多复杂？
- Does the workaround have side effects? / 变通方案是否有副作用？
Quick Reference Card / 快速参考卡
| If... 如果... | Then Severity Is... 则严重等级为... |
|---|---|
| All users can't use the app 所有用户无法使用应用 | Critical 致命 |
| Payment/checkout fails 支付/结账失败 | Critical 致命 |
| Core feature broken, no workaround 核心功能损坏，无变通方案 | Critical 致命 |
| Core feature broken, has workaround 核心功能损坏，有变通方案 | Major 严重 |
| Important feature partially broken 重要功能部分损坏 | Major 严重 |
| Non-core feature broken 非核心功能异常 | Medium 中等 |
| Cosmetic issue 外观问题 | Minor 轻微 |
| Improvement idea 改进建议 | Suggestion 建议 |
Common Mistakes / 常见错误
- Over-severity / 过高定级: Calling every small visual issue "Critical"
- Under-severity / 过低定级: Marking a payment failure as "Medium"
- Confusing severity with priority / 混淆严重度和优先级: Severity = impact, Priority = urgency
- Not considering user perspective / 忽略用户视角: What seems minor to you may be critical to users