Live data from Hacker News

Ask HN: Good, lightweight bug tracking system for small team?

news.ycombinator.com

61–67 of 67 posts

Re: Ask HN: Good, lightweight bug tracking system for small team?

#61
I'm also a Mantis user, and I'm quite happy with it.

Mantis supports Git and SVN integration, if you use the Source plugin. You can find detailed information on how to add these functionalities to Mantis at the following URL: http://leetcode.net/blog/2009/01/integrating-git-svn-with-ma...

Note: Importing repositories with a couple hundred commits will take a while!

I also like FlySpray, but unfortunately, the last commit seems to be 1 year old.

Re: Ask HN: Good, lightweight bug tracking system for small team?

#62

We use Redmine here (~4 people) and it's great. Rails backed, lots of plugin if you need more and easily extendable. It integrate cleanly with CVS, Git, Mercurial, SVN, ... and we'll even do invoicing with it in a few weeks. There are paid hosting options if you don't want to maintain it yourself.

Can you shed some light on Redmine's invoicing? I have not seen any plugins that give that functionality.

We use this one: http://github.com/edavis10/redmine-invoice-plugin. Simple (a bit too simple) but gets the job done and can autofill based on timesheet entries.

Re: Ask HN: Good, lightweight bug tracking system for small team?

#63
post #20

Post-its on a whiteboard.

Your advice is great, but it is too simple and too obvious to be used by any modern team. It is old-fashioned, without any noise and hype around it. Fortunately, the guys at http://73primenumbers.com/ started a campaign to add the missing buzz.

My tech lead from two projects ago used post-its on a whiteboard, and one of the teams I work closely with still does. For search options, we used a 2D-grid, where the vertical axis was the component and the horizontal access was the state of done-ness (unassigned, being worked on, in code review, finished).

If you have a small, colocated team, this is basically ideal. There's low overhead, and the overhead consists of physically taking off a post-it and sticking it in the next column, which feels very satisfying. At a glance, you can see how done the project is - lots of post-its on the left means you have a while to go, lots of post-its on the right mean you're almost done. If you have components that need lots more attention, they'll show up as stragglers on the grid, and then you can either allocate more resources or cut the feature as appropriate. (In our project, that was usually self-allocation, because we didn't have particular engineers assigned to particular components, and each engineer was familiar with a few different components). If a lot of tasks get stuck in the code review stage, you know that it's time to lean on the code reviewers a bit.

Re: Ask HN: Good, lightweight bug tracking system for small team?

#67
http://www.getdonedone.com

It's great for small teams where you don't need a ton of reporting features - and it's focused on real-time responsiblity (who needs to respond to what right now). Google docs/excel aren't efficient because there's too much extra noise (sifting thru bugs that don't pertain to you, not easily seeing what bugs are waiting on you with a question, etc.)

Hope you'll try us out!

-KC

Post reply on HN