History of Tracker Research
Version 4
Tracker Research
A review of available bug database systems
| Product | Technicals | SCM | The Good | The Bad |
|---|---|---|---|---|
| Mantis | PHP + Mysql (postgres and other db's are 'experimental') | NONE | Simple straightforward bugtracking, has been around for nearly 10 years, IN YOUR FACE list of issues - no digging around for things | Ugly, sub-optimal UI |
| Jira | Java 1.5 SDK+ | Fisheye cvs, svn, perforce, git | Very feature complete, "Agile" stuff if you are into deadlines | EXPENSIVE for > 10 people. A monster black hole. Agile cards are weird, and don't go away. Issue listing is always a search. Many clicks to see issues |
| Trac | Python + SQLite or Postgres (mysql experimental) | svn | All the cool kids use it, | Filtered search for listing,wiki is not terribly useful, and can't be disabled. No defaults, milestone oriented. Many clicks to see issues, command line interface for basic tasks like renaming milestones, etc. |
| ActiveCollab | PHP + MySQL | svn (in Corporate version) | Very feature rich - complete project management package, pretty, Ajaxified | Overbearying organization - Project -> Milestone -> Ticket. Drill Baby, Drill. Many clicks to see issues. |
| FlySpray | PHP + MySQL, Postgres | NONE | Jabber Integration, flexible & easy configuration of types of reports, resolutions, configuration, more |