Feedbug

Hi, yes, that's exactly the back and forth Feedbug is meant to cut out.

Angular works fine. Feedbug is a plain script tag, so you drop it in index.html (or inject it from main.ts if you only want it outside production) and it runs in its own Shadow DOM, so it won't touch your styles or your change detection.

Route changes without a reload are handled: the widget watches the URL (history navigation plus a light check every second), so each report is tied to the route the tester was actually on, and the markers for existing feedback reload for each route.

Each report includes:

• a screenshot of the viewport at the moment of submit

• the clicked element (CSS selector path plus its surrounding HTML)

• console warnings and errors

• failed network requests (fetch and XHR, 4xx/5xx)

• uncaught JS errors and unhandled promise rejections

• browser, OS, screen size

• a short session replay of what happened before the click, with inputs masked by default

All of it lands in the Linear or GitHub ticket, so QA only has to click and write a sentence.

One honest caveat: we also try to link the ticket to the source file of the component. That works well with Vue, but on a production Angular build the component names are often lost, so you may not get that link. Everything else above works the same.

Happy to help you set it up if you give it a try