Loading Profile...
Is PivotalTracker suitable as a bug tracker?
We have a small team, but routinely want to keep somewhere around 100-200 bugs/enhancements "on the radar." Has anyone tried using PivotalTracker for this purpose, or is the expected behavior to keep a separate bug tracker, and only use PivotalTracker for managing estimated features?
As a follow up-question, assuming you use both tools, do you pull bugs out of the bug system and into tracker to ensure you have an accurate view of velocity based on the real work being done? Any best practices would be appreciated.
Thanks!
As a follow up-question, assuming you use both tools, do you pull bugs out of the bug system and into tracker to ensure you have an accurate view of velocity based on the real work being done? Any best practices would be appreciated.
Thanks!
I’m thankful
7
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?At a previous company we used Pivotal Tracker as a bug tracker with great success. We often had at least 200 open bugs/chores/stories between current/backlog/icebox.
The caveat: Tracker is really written to work with the Agile workflow Pivotal uses and teaches. I personally think it tends to be a good workflow, but if you've got a different good way of building software, you might or might not find Tracker to mesh with it.
1 person says
this answers the question
-
Inappropriate?For one more opinion (not that it differs much)... We use it as a bug tracker and like it a lot. This is the second company/project I've used it for bug tracking. We used to use Tracker just for project management, and Lighthouse for bugs, but I didn't like having them separate, primarily because if they're all together in Tracker, then you can prioritize the bugs in with the other work, and you always know what is the priority order of work should be, whereas when they're separate you have to explicitly coordinate.
As Jeff said, it may depend on your workflow. If you use more of a waterfall approach and/or have hundreds of bugs open at a time, then it may simply muddy Tracker too much. We rarely have more than a handful of bugs open, so they just slot in with the rest of the stories and chores in priority order. -
Inappropriate?Update: Tracker now has built-in integration with Lighthouse, allowing you to keep all reported bugs/issues in a bug tracking tool, and use Tracker as a prioritization and team collaboration tool. More on that here:
http://www.pivotaltracker.com/help/in...
1 person says
this answers the question
EMPLOYEE
