Bug Rejections & Disputes / Bug 驳回与申诉驳回与申诉

Understanding why bugs get rejected and how to handle disputes.

理解 Bug 被驳回的原因以及如何处理申诉。

Common Rejection Reasons / 常见驳回原因

Reason 原因	Meaning 含义	How to Avoid 如何避免
Not Reproducible 无法复现	Developer couldn't reproduce 开发人员无法复现	Provide clearer steps, specify environment 提供更清晰步骤，说明环境
Not a Bug 非 Bug	Behavior is intentional 行为是预期的	Check requirements before reporting 报告前检查需求
Duplicate 重复	Already reported 已报告	Search existing bugs first 先搜索现有 Bug
Not Enough Info 信息不足	Missing details 缺少详细信息	Complete all required fields 填写所有必填字段
Out of Scope 范围外	Not part of current test 不属于当前测试范围	Review test scope beforehand 提前审查测试范围
Wrong Environment 环境错误	Issue on unsupported setup 在不受支持的配置上出现问题	Test on required environment only 仅在所需环境上测试

How to Dispute a Rejection / 如何申诉

If you believe a rejection is incorrect:

1. Review the rejection reason carefully / 仔细审查驳回原因

2. Gather additional evidence / 收集额外证据

   • More detailed reproduction steps / 更详细的复现步骤
   • Additional screenshots or recordings / 额外的截图或录屏
   • Console logs or network logs / 控制台日志或网络日志
   • Reference to requirements documentation / 引用需求文档

3. Explain clearly why you believe it's a valid bug / 清晰解释你认为这是有效 Bug 的原因

4. Stay professional — focus on the bug, not the person / 保持专业——关注 Bug 本身

Dispute Process / 申诉流程

Bug Rejection Reasons: Explained / 驳回原因详解

Rejection 驳回原因	Description 说明	Prevention 预防措施
Cannot Reproduce 无法复现	Developer followed your steps but couldn't see the bug 开发人员按步骤操作但未看到问题	Add environment, timing, test data details 添加环境、时间、测试数据详情
Works as Designed 按设计工作	Feature behaves according to spec, not a bug 功能符合规范，非 Bug	Always check requirements first 始终先检查需求
Duplicate Submission 重复提交	Same bug already exists 相同 Bug 已存在	Always search before submitting 提交前始终搜索
Missing Screenshot 缺少截图	No visual evidence for visual bugs 视觉 Bug 缺少视觉证据	Always attach screenshots 始终附上截图
Low Quality 质量低	Blurry images, unclear description 图片模糊，描述不清	Use proper tools and templates 使用合适的工具和模板