As most web developers would know, keeping track of bugs can often be a challenge from a project management perspective. We’re not going to beat around the bush, we dislike it a lot ( hate is a strong word ), but Bugherd almost makes it pleasurable.
We’re always on the lookout for tools to help us improve our work-flow and ultimately deliver better results on all our projects. Our old bug tracking system was sorely lacking, so when we heard about Bugherd, we decided to give it a go. After using it on a project, here’s our Bugherd review.
Set it up and start herding them bugs
Bugherd has a simple, clean, fast interface that is a pleasure to use. To start using it on a project you just embed a script in your website’s code, then you’re up and running. Now, you’ll see the sidebar on the website whenever you’re logged into Bugherd.
Highlighting a bug is very simple. Click a bug, write a note, then it’s in the system. From the Bugherd admin panel you’ll be able to categorise and prioritise each bug. You can add additional comments, images and you even see useful information such as browser version, device, OS and window size which is the where Bugherd becomes really powerful.
What else is cool about Bugherd?
One of the great features we find extremely useful is that you can invite people to participate in herding bugs ( great for enthusiastic clients ). Even if you don’t want to invite people, there is a stripped down version which comes in the form of a little ‘feedback’ tab that hovers on the lower right part of your webpage. This tab is able to be used by any website viewers, so you can invite clients and even end-users to provide feedback.
At Stickybeak, we use Basecamp to manage our projects and Bugherd integrates with this nicely. By setting a bug to ‘to do’ it can automatically be added to a ‘to do’ list in Basecamp for the same project ( neat huh? ). It does appear to be a one way street though ( Basecamp doesn’t seem to talk back to Bugherd )… and that’s fine as dealing with the bugs is best done in the Bugherd interface… it’s just nice having a list of bugs to squash arrive in your Basecamp so you can digest them at the start of the day.
What we would like to see?
We use Beanstalk for version control and to deploy our projects. It would be great to see Beanstalk and Bugherd communicate in unison, then you could see which commit / version the comment was made on.
We use Harvest for invoicing and time tracking so being able to accurately monitor how long bugherding takes for each project (in total and per bug) would be great.
That’s it for our Bugherd review. We strongly encourage you to give it a shot on your next project. www.bugherd.com