I promised you to come back and tell you about my milage with Mantis. Although I don’t think it’s the best looking issuetracker there is, it certainly is very easy to use. Things you need are there where you look. It has all the relevant features for me to keep track of my issues.
At the moment I am not working on a “real” project, so I use Mantis as a very sophisticated to-do-list/project-management-tool. I defined the projects I’m working on, and also the thoughts I have that could lead to a real program are defined as projects. Each project has it’s own issue-categories, some of them they all have in common (categories GUI, Error handling, Program logic, Installation, Configuration). Within these categories I define issues that are either bugs, feature requests, tweaks. Because each issue can be stored with a version of your project, it’s easy to define future features.
So far, it has helped me to organize my thoughts and the things I wanted to start, but remained thoughts in my head. I already have 6 projects defined, one of it actually being a project that’s “real” but is waiting for customer input on what to do next (move on to a new and improved version, or declare this version as the-end-of-it).
Thanks Scott, for pointing me in the right direction!