Bug reports that arrive in ClickUp with the evidence attached
Notarus creates a ClickUp task from a bug report carrying confirmed screenshot or video attachments and the source page. A backlink opens the Notarus ticket with its available replay, logs and browser context. ClickUp statuses are per-list and custom, so the Notarus pipeline maps onto the statuses of the list you choose, in both directions.
ClickUp integration
Every integration is on every plan, the free one included. No credit card.
Discount code accepted but total unchanged
- Task name and description
- Attachments
- Ticket backlink
- Source page
- Custom status
What reaches ClickUp
-
Task name and description. The report title and body, with the reporter's steps to reproduce.
-
Attachments. The annotated screenshot, and the screen recording when there is 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.
-
Custom status. Pipeline stages map to the statuses of your chosen list, and movement flows both ways.
How Notarus and ClickUp fit together
ClickUp gives every list its own status set, which is genuinely useful and makes a bug-tracking integration harder than it looks. There is no universal in-progress to map to, because your list's statuses are whatever your team named them. Any integration that guesses will eventually move a task into a status that means something different from what it assumed.
So Notarus reads the real statuses from the list you pick and suggests a mapping from them, which an admin then adjusts. A status that cannot be mapped without ambiguity is left unmapped, and an unmapped status is a logged no-op rather than a guess. That is a deliberate trade: fewer automatic moves, no wrong ones. A sync that occasionally does nothing is recoverable, and one that occasionally moves the wrong task is how a team stops trusting the board.
The ClickUp task carries the report text, source page and confirmed media attachments. The backlink is where a teammate with Notarus project access opens the available replay, console output, failed requests and browser context. Those details stay with the original report instead of being copied into fields ClickUp does not define.
ClickUp nests lists inside folders inside spaces, and the connection is made at the list level for a practical reason: the list is where statuses are defined, so it is the smallest unit at which a status mapping is meaningful. Picking a space would leave the mapping ambiguous across every list inside it, since two lists in the same space can define entirely different statuses. Choosing the list is what makes the mapping a single, checkable decision.
Common questions
How does Notarus handle ClickUp's custom statuses?
It reads the actual statuses from the list you connect and suggests a mapping to the Notarus pipeline, which an admin adjusts. Statuses that cannot be mapped unambiguously are left unmapped, and movement into an unmapped status is logged and ignored rather than guessed at.
Which ClickUp list do reports land in?
The list chosen during setup. Because statuses are per-list in ClickUp, the list choice and the status mapping are one decision rather than two.
Can the same project push to several lists?
One Notarus project connects to one target list, so reports from that project land in one place. Teams that split bugs across lists usually do that with ClickUp's own automations after the task arrives.
Other trackers
Terms on this page: bug triagebug severity vs priorityqa testing
Send your first report to ClickUp.
Every integration is on every plan, the free one included. No credit card.