On Jun 8, 2011, at 2:09 PM, Kevin Baker wrote:
Some tools we were thinking of evaluating are: Rally Pivotal Tracker Red Mine Lighthouse Trac
Bug tracking -- there are innumerable apps/options here, and I think it is for good reason: everybody wants to do it juuust a little different. I've used several, and keep wanting to write my own for that very reason, and I think there's no way around having to try at a few of them for yourself. Trac/RedMine are going to be really similar. IMO, that choice often comes down to how much you want to modify it (and thus whether you want to do that in Ruby or Python). Lighthouse is about as basic as it gets. If that's all you want, it serves pretty well. The core ticket system is OK, the rest is kinda underwhelming. They all have quirks.
I've been using Pivotal Tracker for a couple years. It started as an internal tool (I actually saw it pre-beta back in '06 I think it was), and you could tell by their near stubborness in not making changes that they were determined to have it follow their take on how it should work for their company, and if you wanted to use it too, well great. Lately, since deciding to make it a revenue-based product, they've started to make a number of small but meaningful changes that at least helped the UI. There's still some UI niggles I have with it, and it is missing capabilities to make it more adaptable to varying approaches, but it has served one of my current projects with a small team well enough. Still, there's quite a few features I'd like to see added.
The last time I looked, the choices were either Pivotal, or rather heavy-weight tools. So, Pivotal was kind of the only reasonable option for simplicity if you could deal with it's inflexibility.
I can't tell you how many times I sit down and start to write down a little more of what I would do to build alternatives to these tools....
-- gw -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
