Right-click what is broken. The report writes itself: component, screenshot, logs. Nobody asks you where it was.
The component, its logs, who wrote it and when, and where on the page it was. That is why nobody has to ask.
A verified selector, the framework component that rendered the element and, on development builds, the file and the line.
Author and timestamp on every note. Page, scroll position and viewport too, because layout bugs depend on all three.
Right-click it. The note is anchored to that component and survives a reload.
Drag a rectangle. FrontBug lists every component inside it, ranked by overlap.
Full height in one image, sticky headers handled, with the pins drawn on top.
An unconfigured reporter and a missing favicon are not your bug. FrontBug keeps them, groups them by pattern, and puts the first-party failure that followed your click at the top.
Nothing is discarded. The full log is in the bundle.
Capture, annotate and export on a plane or on a locked-down client network.
Everything stays in your browser until you export a bundle or connect a project.
Whoever finds it works next to the page. Whoever fixes it opens a folder that already says which component broke.
One folder. Readable on its own, and shaped so a coding agent can work straight from it.
A review session is ten notes in ten minutes. Here every note is already a ticket, and every hand that touches it is on the record.
Three notes in two minutes, each anchored to the component that rendered it. The session goes to the project and the team is notified.
Taking it assigns it to him, so nobody else picks up the same work. The board shows who has it and when they last touched it.
It lands in To verify, not in Done. Whoever fixes something is the worst person to decide it works.
One click opens the site, jumps to the component and lays the old screenshot over the live one. She sees it, then closes it.
The check happens on the page, not on a description. That is the part a ticket tracker cannot give you.