Bug Reports
The Bug Reports tab is used to capture issues, reduce duplicates, and route actionable reports to moderators/admins.
Submit Flow
- Open Bug Reports and create a report with title, steps, expected behavior, and actual behavior.
- Add optional evidence (screenshots, notes, repro hints).
- Submit and review similarity suggestions to avoid duplicate entries.
Similarity + Merge
- Reports are grouped by similarity to help moderation.
- Admins can merge similar reports into a canonical issue.
- Merged reports preserve context while reducing noise in the queue.
Moderation
- Privileged roles can review, approve, reject, and merge reports.
- Use clear reject reasons so submitters can improve follow-up reports.
- Prefer merge over reject when a duplicate still adds useful evidence.
Status Model
- Open: newly submitted, needs review.
- Triaged: reviewed and categorized.
- Merged: absorbed into a canonical issue.
- Resolved: fix shipped or no further action required.
Quality Tips
- Include exact steps and recent actions before the issue started.
- Add device/browser information for UI or scanner issues.
- When possible, include specific barcode, source ID, or preset ID to speed up diagnosis.
Edit History
- 2026-04-12: Added dedicated Bug Reports docs page with submission, triage, and moderation flow.
Sources
Based on current Bug Reports workflows in the app runtime.