Connecting a Tracker
OAuth setup for Jira, Linear, Trello, GitHub, GitLab, and Azure DevOps.
Every Project connects to exactly one issue tracker. All six supported trackers use an OAuth popup — there's no API-token-paste option, and no manual field mapping beyond picking the right project/board/team/repo.
The general flow
Pick a tracker
On the Integration tab, click one of the six tracker cards. This immediately opens an OAuth authorization popup for that provider.
Approve access
Log in (if needed) and approve the requested scopes. You'll see status update from Connecting… to Waiting for authentication… to Connected as (your account).
Choose the destination
Depending on the provider, pick the specific project, board, team, or repository that new reports should be created in.
Once connected, other tracker options are hidden for that Project — to switch providers later you'll need to reconnect with a different one, which is treated as changing the integration entirely.
Provider-specific notes
Connects via Atlassian OAuth. After authorizing, choose your Jira Cloud site and then the Jira project reports should be created in. See the Jira integration reference.
Connects via Linear OAuth. Choose a Linear team, and optionally a specific Linear project within it. See the Linear integration reference.
Connects via Trello OAuth. Choose the board cards should be created on. If you use the AI Agent (MCP), you can additionally map each Trello list to a SnagRelay status (Todo / In Progress / Done / Ignore) so the sidebar stays in sync. See the Trello integration reference.
Connects via GitHub OAuth (separate from any GitHub login you use for SnagRelay itself). Search and select the repository issues should be filed against. See the GitHub integration reference.
Connects via GitLab OAuth. Search and select the project issues should be filed against. Self-managed GitLab instances are supported via a configured host. See the GitLab integration reference.
Connects via Azure AD OAuth. Choose your organization, then the project — bug reports are created as Bug work items. See the Azure DevOps integration reference.
Reconnecting
If a connection is revoked or a token expires, the Project shows an "Integration Disconnected" alert naming the provider, on Overview. Reports keep queuing in the background and are delivered automatically once you reconnect — see Integration Disconnected.
Default assignee, statuses, priorities, and labels
After connecting, SnagRelay syncs your tracker's team members, statuses, priorities, and labels so you can:
- Set a default assignee for new reports
- Control which assignees/statuses/priorities/labels are visible as options in the widget's feedback form (via the eye icon on Overview)
- Feed triage rules that auto-assign based on report content
Not team seats
"Team Members" shown on a Project's Overview are synced from your tracker, not SnagRelay accounts. SnagRelay doesn't currently support multi-user teams or SSO on its own — each SnagRelay account is single-owner.