Content and marketing teams spend a lot of time on live websites — publishing, updating, reviewing. They find bugs. Not necessarily JavaScript exceptions or 500 errors, but real problems: broken images, wrong copy that shipped from a stale template, form fields that submit incorrectly, layout breaks on mobile.
Most bug reporting tools are built for dev teams. They send reports to Jira or GitHub, they include stack traces and console logs, and they assume the person receiving the report knows what a status code is. Content teams don't work there, and they shouldn't have to.
What content teams actually need
When a content editor finds a broken paragraph, they need to be able to report it in two clicks and have it land somewhere their team tracks work — usually Asana, Notion, or Trello. They don't need to open a Jira account. They don't need to learn what a console log is.
The report should include a screenshot (so the developer or other editor can see exactly what's wrong), the page URL, and a brief description. That's it. Everything else is overhead that makes people give up and send a Slack message instead.
How routing rules solve the tool mismatch
With SnagRelay, you can connect both Jira and Asana to the same project. When a dev-flagged bug comes in — a console error, an HTTP 500 — it goes to Jira. When a content-flagged issue comes in — wrong copy, broken image — it goes to Asana, where the content team actually works.
The routing is automatic. Whoever submits the report just clicks the widget, selects the feedback type, and submits. SnagRelay routes it based on the type without needing the reporter to know which tool goes where.
Who this is for
This setup works well for:
- Companies with separate dev and content/marketing teams working on the same site
- Agencies that maintain client sites and want content issues to go to the client's Asana, not the agency's Jira
- SaaS products with a dedicated content team managing a marketing site alongside the dev team managing the app
Setting it up
Connect Asana to your SnagRelay project (alongside whatever your dev team uses). In Routing rules, add: Feedback type: Content task → Destination: Asana. Your content team submits reports from the same widget as everyone else — their reports just land in the right place.
