SnagRelay supports multiple integrations per project. This means you can connect Jira for dev bugs, Asana for content tasks, and Trello for client feedback — all from the same project — and define rules so each incoming report goes to the right tool automatically.
What routing rules are
Routing rules are conditions you set at the project level. Each rule says: if the feedback matches this type, send it to this integration. Reports are classified when they arrive, matched against your rules, and delivered — no manual sorting needed.
Step 1: Connect your integrations
In your SnagRelay project, go to Integrations and connect each tool you want to use. You can have Jira, Asana, Trello, Linear, ClickUp, Monday.com, or any combination active at the same time. Each integration goes through a one-click OAuth flow.
Step 2: Open Routing rules
In your project settings, click Routing rules. You'll see a table where each row is a rule: feedback type → destination.
Step 3: Add your rules
Click Add rule and define your first condition. Examples:
- Feedback type: Bug report → Destination: Jira
- Feedback type: Content task → Destination: Asana
- Feedback type: Client feedback → Destination: Trello
Rules are evaluated top to bottom. The first match wins.
Step 4: Set a fallback
Add a final rule with no condition (a catch-all) that routes to your primary integration. This ensures every report lands somewhere, even if it doesn't match a specific rule.
Step 5: Configure field mapping per integration
Each integration has its own field mapping. Click on an integration in the list to configure how SnagRelay fields (priority, assignee, labels) map to that tool's native fields. Jira and Asana can have completely different mappings.
Step 6: Test with a real report
Submit a test report via the widget on your site. Check which integration it landed in — it should match the rule for that feedback type. Adjust rules as needed.
Common setups
- Dev team on Jira, content team on Asana: Bug reports → Jira, Content tasks → Asana, fallback → Jira
- Agency with client projects: Dev bugs → internal Jira, client-visible issues → client Trello board, fallback → Jira
- Startup with Linear + Notion: Dev exceptions → Linear, PM tasks → Notion, fallback → Linear
