Bug Report Attachments / Bug 报告附件报告附件
Attachments provide visual evidence and technical details that make bug reports more credible and actionable.
附件提供视觉证据和技术细节，使 Bug 报告更具可信度和可操作性。Attachment Requirements / 附件要求
| Attachment Type 附件类型 | When to Use 使用时机 | Format 格式 |
|---|---|---|
| Screenshot 截图 | Visual issues, error messages, UI states 视觉问题、错误信息、界面状态 | PNG / JPG |
| Screen Recording 屏幕录制 | Complex reproduction, animation issues 复杂复现、动画问题 | MP4 / GIF |
| Console Log 控制台日志 | JavaScript errors, API failures JS 错误、API 失败 | Text Screenshot 文本/截图 |
| Crash Log 崩溃日志 | App crashes on mobile/streaming devices 移动端/流媒体设备崩溃 | Text file 文本文件 |
| Network Log 网络日志 | API request/response issues API 请求/响应问题 | HAR Screenshot HAR/截图 |
Screenshot Best Practices / 截图最佳实践
- Crop if needed but show context / 可裁剪但保留上下文
- Annotate with arrows or boxes to highlight the issue / 用箭头或方框标注问题
- Capture entire page for layout issues / 布局问题截取全页
- Include browser dev tools when relevant / 相关时包含浏览器开发者工具
- Use timestamp to show when the bug occurred / 使用时间戳
Screen Recording Best Practices / 录屏最佳实践
- Keep it short (under 30 seconds) / 保持简短（30 秒以内）
- Show the full flow from start to bug appearance / 展示从开始到 Bug 出现的完整流程
- Include cursor clicks so steps are visible / 包含光标点击使步骤可见
- Speak aloud if audio helps explain the issue / 如果音频有助于解释问题，请大声说明
Common Rejection Reasons / 常见驳回原因
- Screenshot doesn't show the bug clearly / 截图未清晰显示 Bug
- Missing console logs for JS errors / JS 错误缺少控制台日志
- Video quality too low to read text / 视频质量太低无法看清文字
- No network logs for API-related issues / API 相关问题缺少网络日志