TrustRadius
Centralized Bug Tracker with Screen Capture, Tagging, and Commenting
https://www.trustradius.com/bug-trackingBugHerdUnspecified8.812101
Ariana Thompson profile photo
December 21, 2018

Centralized Bug Tracker with Screen Capture, Tagging, and Commenting

Score 8 out of 101
Vetted Review
Verified User
Review Source

Overall Satisfaction with BugHerd

We're currently using Bugherd to perform UAT and work with the QA team for our backend website development. It's used cross-departmentally, from our tester in departments ranging from operations, to customer support, to marketing. We use BugHerd to capture issues on the website where the site is not performing to our requirements, or if we experience an error. Since there is a language barrier in some cases between QA and UAT, it has allowed us to pinpoint the exact location of the issue and address it fully in our comments. The screen capture feature that integrates and creates a corresponding ticket is an easy and fast way to report technical issues when they're encountered by a non-technical team.
  • The screen capture tool is terrific and allows web-based issues to get added and uploaded without any saving, copying, or resizing.
  • The widget that opens via a Chrome extension is intuitive and it's easy to toggle the feature on and off. If it's on, you can see all the other reported bugs on that page to help your team avoid multiple reports of the same issue.
  • The way the tool creates a new ticket for each bug and then allows you to adjust the status on it is helpful.
  • I enjoy the conversations and tagging features within each bug ticket.
  • The screen capture tool doesn't allow you to custom screenshot certain areas and upload them to your bug ticket. I'd like to be able to encompass a custom area rather than just the text or image or formatting blocks within a page.
  • Occasionally the widget will disappear and you'll have to reload the page in order to see the expandable arrow in the corner.
  • The comment history pings your email for every comment ticket, and it's not intuitive to deactivate this feature for users who aren't following up with a specific bug.
  • This tool has helped us simplify communication with developers in other countries and have conversations about multiple issues all on one platform.
  • We're able to give additional context and clarification when asked and it removes the delay between follow up when the conversation goes directly to the person who reported the issue.
  • The sheer number of bugs we have to log on a massive project made this an ideal choice over a spreadsheet or other kind of tool. The image capture was necessary for the context needed to quickly resolve questions.
I didn't specifically choose Bugherd for this project, but when we do select a company bug tracker, this is the one I will choose. I've used JIRA and Pivotal Tracker previously, both of which had a bigger learning curve than Bugherd, so it wasn't simple for our customer support teams, or non-technical testers to submit bugs and issues easily. JIRA and Pivotal create or encourage the need for a middleman or project manager to sift through things, but Bugherd allows things like prioritization and commenting to encourage direct communication. It might not be ideal for massive companies but is an excellent tool per project and for smaller companies.
Bugherd is well suited to our needs because it's an intuitive tool that doesn't require a ton of training, and we are working with a development agency to improve our backend and communicate issues to developers. From what I've seen, it does require you to use Chrome, which might not be perfect for other companies but it great for us.
The tool has great functionality for tracking and allows you to move bugs into stages like "doing", "done" or "backlog".
The screenshot tool has been super easy to use, and when we do have a bug that requires multiple screenshots, it's easy to open up a newly submitted ticket to attach a custom screenshot. It isn't easy to track down a specific bug you've logged if there are hundreds, so be prepared to dig quite a bit if you're using it for extensive testing and find yourself trying to go back.