Introduction
What SnagRelay is, how it fits into your workflow, and where to start.
SnagRelay is a bug-reporting and QA tool. A small widget (or SDK) captures a screenshot, console errors, network activity, and a session replay the moment someone spots a problem — then delivers a fully-detailed report straight into the issue tracker your team already uses.
The pitch is simple: whoever finds the bug (a QA engineer, a PM, a client, an end user) shouldn't need any technical knowledge to report it, and whoever fixes the bug shouldn't need to ask "can you send me more details?" ever again.
Quick Start
Sign up, create a project, connect a tracker, and install the widget in under 5 minutes.
Core Concepts
Projects, Issues, integrations, and plans — the vocabulary used throughout these docs.
Installation
Web Code, WordPress, or Chrome Extension — one channel per Project.
Access & Reporters
Invite people to report bugs with their own tokens — no dashboard access.
Integrations
Jira, Linear, Trello, GitHub, GitLab, and Azure DevOps.
How it fits together
- Create a Project in your dashboard and connect it to an issue tracker (Jira, Linear, Trello, GitHub, GitLab, or Azure DevOps).
- Pick an Installation channel — Web Code, WordPress, or Chrome Extension. Invite reporters if others need to file bugs.
- Someone reports a bug. They use the widget (or extension), annotate a screenshot, and submit. SnagRelay attaches console errors, network data, browser/device info, and — on paid plans — session replay and reproduction steps.
- The report lands in your tracker, already formatted, with an AI-generated title and (optionally) an assignee and priority set by your triage rules.
- Your team works it in the tracker as usual — with the full report page linked for screenshot, errors, and session context.
One project, one tracker
Today, each SnagRelay Project connects to exactly one issue tracker. If you run separate staging and production environments, create a separate Project (and API key) for each — see Core Concepts.