Integrations Overview

Your SnagRelay inbox is the home for every report, and your coding agent reads from it directly. A tracker is optional. Connect one if your team plans and reviews work there, and each report also opens a ticket, with the inbox linking to it.

Six trackers are supported:

To connect one, open the project's Delivery tab. Most use an OAuth popup. Azure DevOps also supports a Personal Access Token.

Each project connects to one tracker. To send reports to two trackers, use two projects.

Inbox plus tracker

With a tracker connected:

• The inbox still shows every report, with a link to the ticket and a Sent to {tracker} filter (Sent, Sending, Failed).
• Your agent can still read reports over MCP by key, and the tracker's key works too. When it resolves a report through mark_issue_resolved, SnagRelay also comments on the ticket.
• The reporter's status page and "It's fixed" email work the same way as without a tracker.
• If the tracker disconnects, new reports wait and are sent after you reconnect. They're never lost. See Integration disconnected.

What gets sent

Regardless of provider, a created ticket typically includes:

• A title (AI-written if AI titles is on), with any report type prefix applied
• A description with the reporter's message, markup comments, and your custom form fields
• Console and network error summaries, technical info (Device & browser), and reproduction steps
• The annotated screenshot or video, attached or linked depending on the provider
• Assignee, priority, and labels, from the widget form or your Assign new tickets to default on Delivery

Tracker sync on Agency

On every plan SnagRelay creates tickets and syncs people, labels, statuses, and priorities so your form can offer them. Agency adds two-way tracker sync, which keeps statuses and resolution in step in both directions.