4 ms·
Awesome leading question, thanks! BugHerd is a tracker for web developers and designers run within the website you're working on. Part feedback tool, part bug
by toast76 16y ago
Awesome leading question, thanks!
BugHerd is a tracker for web developers and designers run within the website you're working on. Part feedback tool, part bug tracker, part QA tool. It's a bug tracker that engineers, designers, clients and stakeholders can all use. Each group has a different interface meaning no one is ever in over their head. A lot of the stuff you normally have to enter manually is logged/tracked automagically, meaning more often than not a short description is enough to get all the detail you need to reproduce a problem.
- weaksauce 16y agoI like the visual selector similar to firebug or chrome developer tools to select a div or element in the page. Though, my question is, what information are you saving per bug when you are selecting a "feature" of the webpage? It would seem that on any website that is not static that you would need to save the whole page images included for each bug so that you can show the bug at the time of inception or at least a snapshot of the page transformed into an image.
- toast76 16y agoThe problem with taking a snapshot is that it quickly becomes out of date, and as you mention can be different with different content. We use some fuzzy selection methods to select the underlying DOM node that is causing you a problem. When a user goes to look at that bug, they're taken to the actual page and location where the problem occurred. This means that even as the page changes our bug tagging still points to the right place. We also keep tabs on all sorts of user/browser information to ensure a bug can be replicated. We have some more tricks up our sleeve for replicating page state and user data (not yet released).