Bug reports that become Asana tasks with their evidence
Notarus creates an Asana task from a bug report with available screenshots and screen recordings attached. The task links to the Notarus ticket for replay, logs and browser context. The Notarus pipeline maps to sections in the Asana project you choose, so moving a task between mapped sections moves the ticket both ways.
Asana integration
Every integration is on every plan, the free one included. No credit card.
Discount code accepted but total unchanged
- Task name and notes
- Attachments
- Ticket backlink
- Source page
- Section
What reaches Asana
-
Task name and notes. The report title and body, with the reporter's steps to reproduce.
-
Attachments. The annotated screenshot, and the screen recording when one exists.
-
Source page. The report’s page URL; captured browser and viewport details remain on the linked Notarus ticket.
-
Ticket backlink. The Notarus ticket links authorized teammates to the available replay, console and network evidence.
-
Section. Pipeline stages map to sections you choose, and movement flows both ways.
How Notarus and Asana fit together
Asana is usually where the whole team's work lives rather than only engineering's, which is exactly why bug reports reach it in the worst shape. The people filing them are the same people filing everything else, and a bug filed like a task is a sentence describing a feeling: the checkout is not working.
Notarus changes what arrives, not who files it. The reporter stays in the product, marks the page, and the task that lands in Asana carries any confirmed screenshot or video, the source page and a backlink to the ticket. Replay, captured logs and browser details remain in Notarus for the team to investigate. The person who picks it up does not have to start by asking, which is the difference between a task somebody can schedule and a task somebody has to investigate before they can even estimate it.
Asana organises work into projects and sections, so the state map here maps Notarus pipeline stages onto sections of the project you pick during setup. Sections you do not map are untouched, which matters because an Asana project is rarely dedicated to bugs alone.
Because Asana is usually company-wide, the separation between internal discussion and what the reporter sees matters more here than on an engineering-only tracker. Comments on the Asana task stay in Asana. Replies meant for the person who filed the report are written in Notarus and marked public, which is what they see in the portal. Nothing crosses by accident, and that is the property that lets a team be blunt in the task about what actually went wrong while the reporter gets an answer written for them.
Common questions
Which Asana project do reports go to?
The one chosen during setup, with pipeline stages mapped to its sections. Teams usually pick a dedicated bugs project, but any project works, and unmapped sections are left alone.
Do Asana comments come back to the reporter?
No. The reporter follows their report through the Notarus portal, and replies meant for them are written there and marked public. Internal discussion in Asana stays internal, which is the separation most teams want.
Does completing an Asana task close the Notarus ticket?
Checking the completed box alone does not. The sync follows section membership, so move the task to the section mapped to a completed Notarus stage. Moving a ticket in Notarus likewise moves the task to its mapped Asana section.
Other trackers
Terms on this page: bug triagebug life cycleacceptance criteria
Send your first report to Asana.
Every integration is on every plan, the free one included. No credit card.