If your content or marketing team lives in Asana while your dev team is on Jira, SnagRelay can route each report to the right place automatically. This guide walks through connecting Asana to a SnagRelay project and setting up routing rules.
Step 1: Add SnagRelay to your site
Drop the SnagRelay script tag into your site's <head>. One line, no framework dependencies.
<script src="https://cdn.snagrelay.com/widget.js" data-project="YOUR_PROJECT_ID"></script>Step 2: Open your project settings
In the SnagRelay dashboard, go to your project → Integrations. Click Add integration and select Asana.
Step 3: Connect via OAuth
Click Connect Asana. You'll be taken to Asana's OAuth screen — authorise SnagRelay to access the workspace you want to use. You'll return to SnagRelay with Asana connected.
Step 4: Map your Asana project
Select the Asana project where tasks should be created. You can also set a default section, assignee, and due date offset.
Step 5: Set routing rules
Go to Routing rules in your project settings. Add a rule: Feedback type: Content task → Destination: Asana. Reports classified as content tasks will now route to Asana. Dev bugs will continue going to Jira (or whichever other integration you have connected).
Step 6: Test it
Submit a test report via the widget on your site. Check your Asana project — the task should appear within a few seconds with the screenshot, technical context, and any routing labels attached.
Tips
- You can have Jira and Asana both active on the same project simultaneously
- Set a fallback destination for reports that don't match any rule
- Each integration can have its own field mapping — Asana tasks can get different fields than Jira tickets
