[quote]Bugzilla is excellent:
http://www.mozilla.org/projects/bugzilla/
Better suited to a site-wide solution rather than a single project, but well worth looking at.
[/quote]
Bugzilla seems to be one of those “a bitch to get to grips with, but worth it’s weight in gold once you do” apps…I’m basing this on my experience in a past life (pre-games-development) in IBM’s development labs, including some painful years in application testing.
[note: I’m taking into account the kind of development we’re talking about here - small projects etc - and I nod to the people who find bugzilla useless/too much; if it’s not right for you, fair enough, but it seems great for most people] - like IDE’s, you could settle for “notepad with extra features” (and I know people who are very productive with semi-programmers’-editors that are just like that), but you gain immeasurably from using a real, dedicated IDE. Similarly, something like Bugzilla is nearly always “worth it” (although hard to measure the value/increase in productivity)
OTOH, I once spotted an unusual app working VERY well as a bug-tracking tool - CVS. My great fear with using a spreadsheet (or anything similar) [as suggested by someone else] is that you don’t necessarily see ALL the history on a certain bug - and experience has taught that you ALWAYS need to be force-fed all the comments and notes etc on a bug when you’re looking at it. Using only appends to text-files (one per bug/RFE), and then viewing the complete change-history for the file as your default view (may require a decent CVS client - haven’t had to use free CVS clients in some time, so I don’t know what they do well these days), can work beautifully.
Side-note: I’m using Bugzilla on a part-time game-project where the testers are fewer than a dozen friends and family - and it’s already less stressful than life beforehand. However, I was fortunate that a friend installed Bugzilla for me, so I cheated ;).