Bug reports that arrive as Trello cards with the proof
Notarus creates a Trello card from a bug report with available screenshot or video attachments and a ticket backlink for replay, logs and browser context. Trello has no status field, so the sync maps the Notarus pipeline onto lists on your board: moving a card between mapped lists moves the ticket, and the reverse holds.
Trello integration
Every integration is on every plan, the free one included. No credit card.
Discount code accepted but total unchanged
- Card name and description
- Attachments
- Ticket backlink
- Source page
- List position
What reaches Trello
-
Card name and description. The report title and body, with the reporter's steps to reproduce.
-
Attachments. The annotated screenshot, and the screen recording when the reporter made one.
-
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.
-
List position. Pipeline stages map to lists you choose. Moving a card between mapped lists moves the ticket, and moving the ticket moves the card.
How Notarus and Trello fit together
Trello is where a lot of small teams and agencies actually run their work, and its weakness for bug tracking is the same as its strength: a card is whatever you write on it. There is no required field, so nothing forces a bug card to include the browser, the steps or the error. The result is a board of cards that each need a conversation before anyone can start.
Notarus is the structure in front of it. The reporter marks the page, and the card that appears carries the annotated screenshot as an attachment plus a link to the Notarus ticket, where captured replay, console output and failed requests remain available to the team. The card is specific because the capture was, not because somebody remembered to fill in a description.
Status on Trello is position, not a field: a card is in a list. So the state map here maps Notarus pipeline stages to lists on the board you choose, and dragging a card between mapped lists is what moves the Notarus ticket. Lists you do not map are left alone entirely, which matters on a board that also holds work unrelated to bugs.
Trello is also where agencies run client work, and that shapes what this integration is for. The client reports on the site you built for them, the card lands on the board your team already works from, and the client watches their own report progress through the Notarus portal without ever being invited to the board. They see their ticket; they do not see the rest of it.
Common questions
Which Trello list do reports land in?
The one you map to the first pipeline stage during setup, usually an intake or Inbox list. Every mapping is explicit, and unmapped lists are never touched, so a board that also holds non-bug work keeps it undisturbed.
Does moving a card update Notarus?
Yes, when the card moves between lists that are mapped. Moving it to an unmapped list is a logged no-op rather than a guess, which is deliberate: inferring intent from an unmapped list is how a sync moves tickets nobody asked it to.
Can the screenshot be seen on the card?
Yes, the annotated screenshot is attached to the card, so it previews in Trello without anybody opening Notarus. The card links to the Notarus ticket, where teammates with project access can watch any available replay.
Other trackers
Terms on this page: bug triagebug life cyclebug severity vs priority
Send your first report to Trello.
Every integration is on every plan, the free one included. No credit card.