BugHerd

"A no-brainer purchase for any agency or development team"

Comentarios: A pleasure to use. Easy to install and use and it makes QA testing a delight.

Puntos a favor: It removes any ambiguity about bugs and feature requests. Being able to annotate a comment directly on a live / staging website, is a huge perk and something that I now cannot live without.

Contras: The lack of customizable columns in their kanban-style layout is a pity. Not a deal breaker, but our agency workflow does not follow a 'backlog', 'doing', 'done', 'closed' workflow and we end up having to have internal discussions about what 'backlog' actually represents in our own workflow. Would be great to rename these columns and have more/less of them.

"Fast bug tracking for bulk bugs, with slow development of new features"

Comentarios: I've been using BugHerd for around 3 years now on large scale web projects, often with 500-2000 bugs reported throughout the project life. I've recently tested all of the key bug tracking tools available for website development, and BugHerd is hands down, still the fastest and most useful tool for bug reporting with a useful user area for bug management. The tool could be so much better though if the dev team behind it invested some more time and resources to make bulk bug management and integrations better.

Puntos a favor: Fast bug reporting with easy to set tags, users and descriptions. Easy to filter user area with kanban columns, search and the ability to go click on a bug and be anchored to a pin in the bugs location on your website. No need to install code for each website you test.

Contras: The development team is very slow to update and make changes to BugHerd. BugHerd is lacking bulk select features, and their connections to third party tools with better backend management aren't up to scratch.

"A Real Game Changer for Web Dev"

Comentarios: Clients have really leaned into this platform. The level of transparency it provides is a big deal for them and allows us to work alongside them rather than play the interpretation game. I'd suggest it to any team that handles large website builds or even simple landing page designs.

Puntos a favor: BugHerd has been a pretty big game changer when it comes to my team's web development capabilities. While we used to have to add significant notes to PDFs and emails to send to the client (and vice versa), now we can tackle changes and feedback right at the source. The tool is fairly simple to use and makes it easy for our clients to give us their thoughts, which has made our timelines shorter and deliverables easier to fulfill.

Contras: Since BugHerd is still being refined and updated pretty frequently, there are the occasional hiccups. It still has some quirks with multiple website testing instances that tend to cross some wires in the feedback. The ability to add a voice recording or brief screen recording to really lock down feedback would be great. When working with a team in a different area, adding bugs to your site can be interpreted a million different ways, so an easier way to provide specific info would be the next evolution of BugHerd.

"Great for client and QA collaboration"

Puntos a favor: This is a great tool for when you want clients and quality assurance testers to be able to mark items that needs attention.

Contras: Needs more (built-in) integration with major bug tracking softwares. Marker can sometimes point to a wrong location but screenshots can also be taken when creating an issue as a solution to that

"Nice UI. Not compatible with responsive websites, however"

Comentarios: Easy for the client to log bugs and to view details about the bug without having to go back to the client to ask more questions and it automatically takes a screenshot from the client's computer when logging the bug.

Puntos a favor: I like the nicely designed UI which allows you to use drag and drop mouse movements to move jobs from in progress to completed etc.
I like how you can comment on items and how the client can respond. You can see the client's browser, OS and screen size automatically so you don't need to ask the client themselves!

Contras: When the client logs a bug in a responsive view and you load the bug task in a full desktop view, hidden mobile elements that aren't available in the desktop view are also hidden. It's not easy to know they are talking about the mobile view without manually checking the screen resolution every time you view a new bug.
The extra client details are only accessible if the client installs the BugHerd browser plugin.