Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

41–50 of 67 posts

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

#41

Post by dtran »

elliottkember wrote: post #23

I've been building Speckle ( http://speckleapp.com ) for a little while: a to-do list with multiple checkboxes per item. it's reasonably light-weight - I don't know whether it suits what you're looking for, but Id be interested to know what you think :) Edit: epi0Bauqu beat me to it!

Reminds me a lot of doodle from the screenshot. Will check it out - maybe I'll start using this instead of Google tasks for my own personal to-dos since that usually is such a long list sitting on top of my google calendar that I can't see my calendar -_-

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

#42

Post by CraigBuchek »

1331 wrote: post #17

Flyspray is as advertised: "uncomplicated." If you want a simple system, it is worth a try. http://flyspray.org/

+1 for FlySpray. It's PHP-based, and pretty easy to install and set up. It does take a few minutes to set it up to add your desired Task Types (TODO, Bug, Feature Request, etc.) and Categories. But once you've done that, it's quite easy to use, and looks pretty good too.

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

#43

Post by dtran »

gaustin wrote: post #35
m0nty wrote: post #16

Earlier quoted context omitted.

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?

I don't have any more time for side projects, but lots of students in one of my HCI classes have built software to do stuff like this in a relatively short timespan (~4 weeks): http://www.youtube.com/watch?v=5s5EvhHy7eQ

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

#44

Post by elliottkember »

dtran wrote: post #41
elliottkember wrote: post #23

I've been building Speckle ( http://speckleapp.com ) for a little while: a to-do list with multiple checkboxes per item. it's reasonably light-weight - I don't know whether it suits what you're looking for, but Id be interested to know what you think :) Edit: epi0Bauqu beat me to it!

Reminds me a lot of doodle from the screenshot. Will check it out - maybe I'll start using this instead of Google tasks for my own personal to-dos since that usually is such a long list sitting on top of my google calendar that I can't see my calendar -_-

I hadn't seen Doodle before - it's quite interesting! A similar layout, but a different objective.

Maybe it's me, but I found it's quite hard to figure out what on earth Doodle is based on its homepage. That's why I like having an in-action screenshot on the homepage, and a "sign up with one click" button. Hopefully Speckle is a little more obvious.

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

#45

Post by dtran »

sidmitra wrote: post #12
sidmitra wrote: post #11

Earlier quoted context omitted.

Redmine, is a good alternative.

Or try Unfuddle, which is sort of like hosted redmine. They have a freemium model, free for 2 users, unlimited repos.

Wow I actually LOVE this hosted solution - minimal setup, easy to customize (can create versions/comps/severities with minimal effort. What really puts it over the top for me is the widget. I'm pretty sure that's going to 1.2x my productivity in terms of knocking out bugs =)

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

#46

Post by andrewl »

andrewcooke wrote: post #29

I 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 want to dig into Fossil as well. And I'm impressed that SQLite moved to Fossil in September 2009:

"Version 3.6.18 - Beginning with this release, the SQLite source code is tracked and managed using the Fossil distributed configuration management system. SQLite was previously versioned using CVS. --http://www.sqlite.org/news.html

And this page on the design of Fossil is interesting:

http://www.fossil-scm.org/index.html/doc/tip/www/theory1.wik...

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

#49

Post by texel »

shadow wrote: post #48

Try Lighthouse, http://lighthouseapp.com/ Been using it and it's great

Agreed. Not only that, but they have an awesome API. I've used it to write automation tools for our build/deploy process. Never underestimate the usefulness of a good API.

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

#50

Post by scorpioxy »

huherto wrote: post #40
scorpioxy wrote: post #25

There'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?

Yes, it would be more general. Although an issue tracker can be used as a bug tracker(look at Trac).

So typically, a bug tracker would be geared more towards programmers and software bugs, while an issue tracker is usually more friendly towards non-programmer users(so would include stuff like knowledge bases, wikis...).

In practice, the distinction is not as clear cut as the definition implies.

Post reply on HN