Working with Bug Reports
Overview
Where captured reports actually show up — there are two different views.
Unlike a typical single "inbox", captured reports show up across two different surfaces in SnagRelay, each suited to a different job.
| Surface | Where | What it's for |
|---|---|---|
| Logs | Project → Logs | Delivery status — did the report reach your tracker? |
| Report page | Public URL, linked from the tracker issue | The full diagnostic view — screenshot, errors, repro steps, session replay |
No in-dashboard bug detail view
There isn't a rich "click a bug to see its screenshot" view inside the authenticated dashboard. That detail lives on the public report page, which is linked from both Logs and the tracker issue itself — this is intentional, so anyone with the link (including people without a SnagRelay login) can see full context.
Typical workflow
- A report comes in → check Logs to confirm it synced successfully.
- Click "View in..." to open the actual tracker issue, or open the report page directly for the full diagnostic view (screenshot, console/network errors, reproduction steps, session replay, AI context).
- If you use the AI Agent, pull a report straight into your VS Code / Cursor extension and resolve it from there — there's no separate dashboard view to track fixes in progress yet.