It has been about 1.5 years since I investigated bug trackers, and the software packages may have grown features/fixes since.
In my mind the choice of bug trackers comes down to who is the intended audience for it. Is it used for tracking issues by just the developers, or do end users also have access to it (You need a straightforward reporting method - users get very confised)?
You didn't say if you want to use a web-based tracker, or a desktop based version.
Briefly some of my thoughts on some web based trackers:
- Flyspray - I discounted this because it didn't support custom fields at the time. A quick googling shows this feature is in development.
- Trac - Horribly confusing for my bug reporters. Has so many features that's easy to get sidetracked into other parts (such as wiki) and content sprawl. Difficult to theme if you have a standard layout for a public site. It has a very cumbersome flow from visiting the tracker to getting an issue filed properly.
- Mantis - At first it looks really ugly but I've been overjoyed with it. It supported custom fields like I wanted. It was SO customisable. A limited amount can be done through a GUI but there are an insane number of items that can be configured through the config file. A downside to mantis was the awful documentation.
Mantis does have some SVN integration if you're willing to dig through the source code and set it up manually. It's possible setup a SVN commit hook to automatically resolve bugs in the tracker that contain strings like "fixed bug 25" (again, customisable through regular expressions) or a bug is referenced in commit messages, that commit can be added automatically as a note to the bug. (This is in the manual)
I also really liked mantis security groups. It's very flexible when you look at the config files (useful if you have end users submitting say sensitive attachments and only want devs/admins to access it), etc...
In my mind the choice of bug trackers comes down to who is the intended audience for it. Is it used for tracking issues by just the developers, or do end users also have access to it (You need a straightforward reporting method - users get very confised)?
You didn't say if you want to use a web-based tracker, or a desktop based version.
Briefly some of my thoughts on some web based trackers:
- Flyspray - I discounted this because it didn't support custom fields at the time. A quick googling shows this feature is in development.
- Trac - Horribly confusing for my bug reporters. Has so many features that's easy to get sidetracked into other parts (such as wiki) and content sprawl. Difficult to theme if you have a standard layout for a public site. It has a very cumbersome flow from visiting the tracker to getting an issue filed properly.
- Mantis - At first it looks really ugly but I've been overjoyed with it. It supported custom fields like I wanted. It was SO customisable. A limited amount can be done through a GUI but there are an insane number of items that can be configured through the config file. A downside to mantis was the awful documentation.
Mantis does have some SVN integration if you're willing to dig through the source code and set it up manually. It's possible setup a SVN commit hook to automatically resolve bugs in the tracker that contain strings like "fixed bug 25" (again, customisable through regular expressions) or a bug is referenced in commit messages, that commit can be added automatically as a note to the bug. (This is in the manual)
I also really liked mantis security groups. It's very flexible when you look at the config files (useful if you have end users submitting say sensitive attachments and only want devs/admins to access it), etc...