Bugs · Software tools

What are your current favorite tools for bug tracking?

Ellen Raynor

April 14th, 2015

What bug tracking tool would you currently recommend for a team that has outgrown managing bugs with google spreadsheets, but has limited budget, and limited time to configure a system?

The ability to screenshot a feedback report using HockeyApp is great, but difficult to manage.

It would be nice if we could manage our sprint stories in the tool as well. We have not been happy with sprint.ly or planscope.io.

Anthony Zeoli Digital Strategy and WordPress Consultant and Trainer

April 14th, 2015

Also, if you're planning sprints, I would look into JIRA w/ Grasshopper. A great system for agile project/product management.

Paul Travis Multifaceted Online Executor: Product Marketing to Program Mgmt. to Business Development

April 15th, 2015

Ellen, I've been happy with http://BugHerd.com .

Amir Yasin Developer, Architect

April 14th, 2015

Try Trello. It's very simple to use and it's free until you grow fairly large. 

Anthony Zeoli Digital Strategy and WordPress Consultant and Trainer

April 14th, 2015

I generally use BugDigger for my issue tracking. It allows you to screenshot bugs, annotate them, and also send them into your project management system. It syncs with Basecamp and JIRA, as well as others. I found it to be quite useful when I needed it.

Tom Maiaroto Full Stack Consultant

April 14th, 2015

I'd always suggest GitHub when possible (if you are using GitHub for your project's codebase). JIRA is fine, but has too many options that all do the same thing (and hidden features in its UX)...But it'll also work.

Honestly the best bug tracking software I've ever seen was trac.

You need to host it yourself though. It's been around for a while (written in Python) and it's not the prettiest (though there's some themes you can apply)...But it is hands down the best bug tracking/PM tool I've ever seen. It's sad that you don't see people using it more often. I think that's due to its design and the fact it's open-source. There's no company pushing and selling it, but it beats JIRA any day.

There's a plethora of plugins for trac as well.

Perri Gorman Founder of Archively & UnrollMe

April 14th, 2015

You can use pivotal tracker or set up an issues repo in github. We do both.

Stefan Gomez Entrepreneur, Engineer & Product Builder

April 14th, 2015

We use GitHub Issues. In combination with waffle.io, you have a complete scrum workflow. It's free and super easy to manage. Have used Trac and Fogbugz in the past and as long as you have someone to keep it organized those can work well too.

Lastly, default (and custom) integrations with slack has greatly reduced dependence on emails for so much of these tools!

Alex Konov

April 14th, 2015

Here is one tool which I would NOT recommend - Atlassian JIRA hosted edition. 2 major problems with it:

1) - hosted edition is extremely unbearably slow like I have not seen since 1995. Like you hit a link and wait 20 seconds for page to reload. It is slow every single time. And I am using it for 5 months already - it fluctuates from terrible to worse and back. I just don't have time to research an alternative, but trust me I would move away from it after current projects are shipped.

2) - their UI is flooded by options menus and buttons. My workflow is really simple, but I have to carefully navigate that mess as a mine field. To do 3 simple tasks that I do 99% of time.

Other than that, it works OK as a bug tracker, but I would definitely try some other tool next time.





Karl Schulmeisters CTO ClearRoadmap

April 15th, 2015

Visual Studio Online.   Not sure given that MSFT is giving away Bizspark access to Visual Studio for startups that anyone would even start with tracking them in Google Spreadsheets.   

Your team is going to be (or should be) developing in Eclipse or Visual Studio.  So your code should reside in either GitHub or Visual Studio Online - regardless of the platform you will be executing the code on.

Both GitHub and Visual Studio Online have Agile, Scrum and Waterfall workflows built in.

Personally I am a great fan of Visual Studio but I understand that this is more of a 'what you grew up with' issue.   But it is a great mistake not to be using a source code repository with formal check in and out requirements even for small projects.  Why?  Because you need a way to roll back to a known good state... always


Mark Travis Product Management Advisor | Speaker | Strategist

April 15th, 2015

I highly recommend Assembla It has issue tracking, story tracking, and you can set up a code repository using git or svn architectures. Just point the developer tools to it. You can track code commits against stories and issues. 

I've used Rally, which is good, but it didn't include the code repository function. One person on the team where we used Rally really liked Pivotal Tracker the best, but Rally was a political decision. (Though not a bad decision)