I'm currently working on a web app builder called AppRabbit (http://apprabbit.com) and used it to create my bug/issue tracking system for tracking my progress with...it. I'm still working on finishing up a few fairly fundamental features, but you're welcome to try it out if you'd like a beta invite. Shoot me an email if you (or anyone else) is interested in seeing what it can do. admin@apprabbit.com.
Ask HN: Good, lightweight bug tracking system for small team?
31–40 of 67 posts
Re: Ask HN: Good, lightweight bug tracking system for small team?
#32We 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.
Re: Ask HN: Good, lightweight bug tracking system for small team?
#33I haven't used it, but this is "interesting" - http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki (I use Trac myself, and it's OK, but not wonderful - haven't found anything better, but will be trying Redmine after reading comments here). [edit: also, you can do bug tracking with Google code, which I am surprised no-one else has mentioned]
I agree, Fossil seems very interesting. I'm just waiting for a chance to try it.
Re: Ask HN: Good, lightweight bug tracking system for small team?
#34http://www.codebasehq.com/features/tickets-milestones
Codebase has a nice feature - you can modify tickets from your commit messages.
Re: Ask HN: Good, lightweight bug tracking system for small team?
#35Earlier quoted context omitted.
You probably meant this as a joke, but I have a friend who is hyper-organized with all of her to-dos on a whiteboard... different sections are different things/different priority levels. Maybe we will hack together a Wii whiteboard Johnny Chung Lee style and use virtual post-its! ( http://johnnylee.net/projects/wii/ )
You probably meant that as a joke too, but I think a virtual whiteboard with Post-Its would be a great product. Colour-coded notes to indicate priority, clustering by physical location on the screen, larger text sizes for very-urgent-do-it-today tasks. You could draw lines on the whiteboard to show the relationship between notes, could have the ability to roll back to previous days to track history, attach files to P…
I think it could be a great product too.
Anyone working on it and want help?
Anyone want to work on it with me?
Re: Ask HN: Good, lightweight bug tracking system for small team?
#36+1 for redmine
We (~7 people) migrated away from trac and use redmine for several projects with subversion and now git. Working very well since 3 years.
A friend of mine uses indefero and was happy with it. Link: http://www.indefero.net/open-source/
Re: Ask HN: Good, lightweight bug tracking system for small team?
#37Our three man team recently took advantage of the FogBugz YC offer and gave it a try. There were some things we liked about it, but in the end it felt too heavy for us. It was more of a support ticketing system than an easy way for a small team to track their bugs (although it would probably be good if you had a lot of external users reporting bugs).
The other problem was that even a lot of custom tweaking, we never quite got the email subsystem working the way we wanted. We finally started using a plugin to make sure we all got emailed on every change, but then we got swamped because we couldn't figure out how to make it send only one email if you changed multiple fields on a ticket. It always wanted to send one for each piece of data that changed.
Before that, we'd been using a Google Docs spreadsheet, doing pseudo-joel-spreadsheet for project tracking and keeping a simple list of bugs.
Now we're using Wave and treating it as a digital whiteboard. It's got its share of bugs still, but I've been really happy.
We've got one wave where we do project tracking (including moving little name markers around, so we can all see real time what everyone is working on. And we've got another wave for bugs with same rules.
We don't put nearly as much info in our wave as we used to put in the spreadsheet (we did a lot of effort estimation and completion time tracking), but the simplicity may actually be helping us keep on top of it better.
And it's awesome to collaboratively rework our goals for each release and at any time we can just scroll through our bug list.
Re: Ask HN: Good, lightweight bug tracking system for small team?
#38mylyn makes bugzilla a lot easier to use if you use eclipse.
Re: Ask HN: Good, lightweight bug tracking system for small team?
#39You might check out Garret Dimon's http://sifterapp.com . I think it's what 37signals would make if they made bug-tracking software.
I use Sifter and love the way it looks and works, but the lack of any kind of API is starting to get on my nerves.
Re: Ask HN: Good, lightweight bug tracking system for small team?
#40There's a difference between a bug tacker and an issue tracker. Bugzilla works great as a bug tracker but is not a great issue tracker. Trac, the opposite. From what you described, seems you're looking more for an issue tracker or a project planning sort of thing. I've liked Redmine, though I haven't used it professionally yet.
Can you elaborate? What is the difference? Is it that an issue tracker is more general than a bug tracker?