Task Manager Product Comparison and Feature Analysis
Basic Features |
WREQ |
JitterBug |
BTT |
PHPTT |
IRM |
The Winner! Request Tracker (RT) |
Mantis |
phpGroupWare |
AceProject (Websystems Inc.) |
Double Choco Latte |
Agstools |
BugRat |
Bugzilla |
Debian |
elementool |
PHP Helpdesk |
Contact info: |
|
Email based system, no db |
|
|
Yann Ramin & Keith Schoenefeld irm@schoenefeld.org |
Unavailable |
|
|
Model for UI |
|
|
|
|
|
|
|
Demo info: |
|
|
|
|
demo |
demo |
demo |
|
demo |
good |
|
|
|
|
|
demo |
Evaluated by: |
DMH |
Ben |
DMH |
Puck? |
Jiong |
Jiong |
Will |
Ryan |
Jiong |
Barnel |
Barnel |
Barnel |
Jim |
Ryan |
Ryan |
Jiong |
0: Rank/Status |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1: Record a task entry in database |
Yes |
|
Yes |
|
Yes |
Yes. |
Yes |
Yes |
Yes |
Yes |
|
|
|
Yes |
Yes |
Yes |
2: Display a task queue a. By task number b. By requester c. By processor |
a.Yes b.Yes c.Yes |
|
a.Yes b.Yes c.Yes |
|
|
|
a.Yes b.Yes c.Yes |
a.No b.Yes c.No |
|
|
|
|
|
a.No b.No c.No |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Yes |
3: Assign processor to task |
Yes |
|
Yes |
|
Yes |
Yes |
Yes |
No |
Yes |
|
|
|
|
No |
Yes |
Yes |
4: Update task status |
Yes |
|
Yes |
|
Yes |
Yes |
Yes |
Yes |
Yes |
|
|
|
|
Maybe...probably not |
Yes |
Yes |
5: Easy to use: a. UI for requester b. UI for processor c. UI for administrator |
a.Yes b.Yes c.Yes |
|
a.Yes b.Yes c.Yes |
|
a. Yes b. Yes c. Yes |
|
a.Yes b.Yes c.Probably |
a.N/A b.N/A c.N/A. It looks like this one is not very group oriented....As far as asigning tasks to other users.
|
a. b. Yes c. Yes |
|
|
|
|
a.HTML form b.email only c.email only This is geared more towards developers.....Not incredibly user friendly |
a.Good b.Good c.Good |
a. Yes b.Yes c.Yes |
6: a. Free software b. Open source c. Support free server d. Support free database e. Free programming language |
a.Unknown- cannot find licensing info b.Yes c.Yes d.Yes(GDBM) e.Yes(Perl) |
It's GPL. basic webserver and cgi setup; no DB |
a.Yes, GPL b.Yes c.Yes d.Yes, although obscure (MNesia) e.Yes, super-obscure (Erlang) |
|
a. Yes. b. c. Yes, run on the Apache web server. d. yes, mySQL(3.22 or above). e. PHP3(3.0.7, 3.0.8, 3.0.12+)/PHP4(IRM 1.3.x and above requires PHP4). |
a. Yes. But pay for support contract. b. yes c.Yes, Apache web server. d. yes, mySQL v3.23.38 or higher e. yes, Perl. |
OS: Windows, MacOS, OS/2, Linux, Solaris, the BSDs a.Yes b.GPL c.Apache, IIS d.MySQL e.PHP (PHP3 and PHP4) |
a.Yes(GPL) b.Yes c.Yes(Apahce) d.Yes(MySQL) e.Yes(PHP) |
a. Yes. But the free portion is limited to is limited to 2 projects, 5 users, and 50 tasks per company. b. No. Pay for the source code. c. Yes. A web server equipped with Internet Information Server 4.0 (IIS) or higher. d. No. Need Microsoft Access 2000 database or Microsoft SQL Server 2000 database. e. |
|
|
|
|
a.Yes b.Yes c.Yes d.should be e.Yes |
a.Yes, and no, tiered sales model, basic is free,
other levels cost money but add features b.No c.runs off of their server d.runs off of their server e.N/A |
a. Yes b. Yes c.Probably. Just mention 'a web server' d.Yes(MySQL) e.Yes, PHP |
7: Web-based |
Yes |
Yes.The whole system is a single C program running as a CGI script |
Yes |
|
Yes. |
Yes. |
Yes |
Yes |
Yes. |
|
|
|
|
yes, in that you can requst via a form on the web, and update tasks, and revieve tasks via email |
Yes |
Yes |
8: Dependable a. Actively used b. Being actively developed and supported c. Has a detailed installation procedure |
a. Not known- maybe used in Duke's math department b.Last update was 2/23/2000 c. Yes |
|
a.Unknown b.Unknown when last updated c.Yes |
|
a. Partially, used by three organizations and advocated by one organization. b. Partially. An announcements & discussion list are provided for new release and help on installation. c. Yes. |
a. Yes b. Yes c. Yes
|
a.Not sure, seems to work well though b.In beta release, actively under development, originally released in
November 2000 c.Yes, really well documented overall |
a.Looks like it b.Last release file dated, 7/26/2001 c.Yes |
a. yes b. yes c. yes |
|
|
|
|
a.Yes b.Yes c.Yes |
a.Unknown b.Unknown c.not required to install...runs off their servers |
a. The author use it in his job. b.last version was released on 8/2/2001. And this project is undergoing major reconstruction. c.Yes |
9: Email the user with a 'ref number' automatically |
|
Audit trail capability |
|
|
|
Yes. The user can refer to in further correspondence about this issue. |
Looks easily possible. |
No |
|
|
|
|
|
Yes |
Unknown |
No |
10: Email task notification to processor |
|
Yes |
|
|
|
Yes. RT forwards the email to a set of staff members. |
Seems already implemented |
Can't tell |
Yes. Email notification when tasks are added or updated. |
|
|
|
|
Yes |
Yes |
No |
11: Performance: a. Multi-user system |
a.Yes |
|
a.Yes |
|
a.Yes. |
a.Yes. |
Unknown, but reports runs on Pentium machine w/o difficulties |
Yes |
a.Yes. |
|
|
|
|
a. Only needs 1 user on host, has its own multi user system |
yes |
Unknown |
12: Provide secure service |
Yes, password and HTTP authentication |
Uses your web servers built-in authentication |
Password auth, unsure if crypto is used |
|
rudimentary authentication |
Yes. Granular access control system. |
Unknown |
Password authentication, and I assume you could always block/allow hosts with access |
Yes. |
|
|
|
|
Unknown |
Should be... |
Unknown |
13: Automated task execution: a. With echoing into task notes field |
a.No |
|
a.No |
|
|
|
Not sure, but looks possible a.Also looks possible |
No--not apparent anyway |
|
|
|
|
|
No |
Yes |
no |
14: Metrics: a. Most frequently requested b. Time to task completion |
a.Yes b.Yes |
|
a.Yes b.Yes |
|
|
|
Lots of reporting available. a.Not sure what this means? You can see frequencies by category,
priority, requester, etc. b.Yes |
|
|
|
|
|
|
a.No b.No |
a.Unknown b.no |
no |
15: Archive |
Yes |
|
Yes |
|
|
|
There is an Archive option listed, but I'm not sure
it actually archives stuff into another location. |
|
|
|
|
|
|
Yes |
Yes |
yes |
16: Task notes field |
Yes |
|
Yes |
|
|
|
Yup! |
Yes |
|
|
|
|
|
Unknown |
Yes |
yes |
17: Search facility |
Unknown |
Search Capability (RegEx compatible) |
Unknown |
|
|
|
Yes |
No |
|
|
|
|
|
Yes |
Yes |
No |
18: can receive tasks from OPG web form: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
19: Maintenace: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
NOTE:
WREQ is a nice package as it has several cool features:
1) Automatic FAQing service
2) requests handled by web and email
3) System logging and metric tracking
BTT looks to be a fairly complete tracking system, but
uses a language and database that no one has ever heard of.
It may be a worth looking at, as the people who did it
seem to know what they are doing, but good luck trying to
convince anyone except a weirdo CompSci person
to try to maintain it.
Debian Bugtracker isn't very user friendly.
Elementool is based on a tiered pay
model, and appears to host the product on their own servers, which is bad
if they go down/out of business we lose.
Keystone was acquired by another
company from the original developer and has since been abandoned. stonekeep
consulting who was hosting the page on keystone says not to bother with it
and to try RT instead.
Basic Features |
TouxDoux |
Roundup |
ProManager |
GNATS |
Teacup |
Tacker |
PHPSAT |
Job Control System |
Scarab |
Contact info: |
|
|
|
|
|
|
|
|
|
Demo info: |
|
|
|
|
|
|
|
demo |
|
Evaluated by: |
DMH |
DMH |
DMH |
DMH |
Will |
Will |
Will |
Jiong |
Jiong |
0: Rank/Status |
|
|
|
|
|
|
|
|
|
1: Record a task entry in database |
Yes |
Yes |
Yes |
Yes |
Yes, by web or email. |
Yes. by web only |
|
Yes |
|
2: Display a task queue a. By task number b. By requester c. By processor |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a. Yes b.Perhaps not as easy c.Yes |
a. Surprisingly not, may be possible to configure to do it. b.Yes c.Yes |
|
Probably. There is a "database content' button on the interface. |
|
3: Assign processor to task |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Yes. |
|
4: Update task status |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Unknown |
|
5: Easy to use: a. UI for requester b. UI for processor c. UI for administrator |
a.Yes b.Yes c.Yes |
a. No-bugs requests are issued via email b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Probably |
a.Yes b.Yes c.Probably |
|
|
a. unknown b.yes c.unknown |
|
6: a. Free software b. Open source c. Support free server d. Support free database e. Free programming language |
a.Yes b.Yes c.N/A d.Yes (PostGres) c.Yes(C++) |
a.Yes b.Yes c.Yes d.Yes (internal database) e. Yes(Python) |
a.Yes b.Yes c.Yes d.Yes(PostGres/Mysql) e.Yes(PHP) |
a.Yes b.Yes c.N/A d.Yes(internal) e.Yes(C,Perl) |
a. Yes b.GPL c.Developed on and tested with Apache 1.3.9 d.PostgreSQL 6.5.2 or later recommended
e.Perl 5.003 is recommended |
OS: Windows, Solaris, Linux, FreeBSD? a.Yes b.Yes, Zope Public License, GPL compatible
c.Yes.Apache d.Zwiki pages, not sure what underlying database is, if any
e. Zope / Python |
|
a. yes. Support can be purchased from Bynari International
b. yes c. yes. The server resides on a Linux operating system using Apache's web server.
d. it uses flat file database. Interconnection with popular open source and commercial databases, and enhanced reporting capabilities will be added. e.Done up with Bourne-shell CGI scripts.
|
|
7: Web-based |
No-GNOME based |
Tickets are viewable view the web, but issued via email |
Yes |
Yes.GNATS is unix console based- GNATSWeb is a seperate
package that makes it web based |
Yes |
Yes |
|
Yes |
|
8: Dependable a. Actively used b. Being actively developed and supported c. Has a detailed installation procedure |
a.Perhaps, but more for project management and not bug tracking b.yes c.yes
|
a.Still in beta b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a.Yes b.Yes c.Yes |
a.Not sure b.Being actively developed and supported
Released on May 1, 2000, with doc updates on May 2, 2000,and apparently no changes since then
c.Yes, really well documented overall |
a.Probably. b.Email list has 26 people on it, so it seems
active. c.Yes, documented |
|
a. unknown b.yes c. yes |
|
9: Email the user with a 'ref number' automatically |
No |
Yes |
No |
Yes |
I think so. |
I think so. |
|
no |
|
10: Email task notification to processor |
No |
Yes |
No |
Yes |
I think so. |
Yes |
|
no |
|
11: Performance: a. Multi-user system |
a.Yes |
a.Yes |
a.Yes |
a.Yes |
Unknown |
Unknown |
|
Unknown |
|
12: Provide secure service |
No |
Yes |
Yes |
Yes |
Unknown |
Username and password administration |
|
Don't know |
|
13: Automated task execution: a. With echoing into task notes field |
a.Unknown |
a. No |
a.No |
a.No |
Not sure, but looks possible a.Also looks possible |
Not sure, but looks possible a.May be difficult until incoming data interface added. |
|
Unknown |
|
14: Metrics: a. Most frequently requested b. Time to task completion |
a.Yes b.Yes |
a.No b.No |
a.Yes b.No |
a.No b.No |
Some reporting available. a.Not sure what this means? You can see frequencies by
priority, requester, etc. b.Not sure |
Some reporting available, but couldn't access it without obtaining account.
a.Most frequently requested b. Time to task completion |
|
no |
|
15: Archive |
Yes |
Yes |
Yes |
Yes |
Nothing mentioned. |
Nothing mentioned. |
|
Nothing mentioned. |
|
16: Task notes field |
Yes |
Yes |
Yes |
Yes |
Has a log function which might function as a task notes field |
Not sure. |
|
Yes |
|
17: Search facility |
Yes |
No |
No |
Yes(including regular expression search!) |
Yes |
Yes |
|
yes |
|
18.Can receive tasks from OPG web form: |
|
|
|
|
Yes, via web-generated email if nothing else |
Currently does not accept incoming email,looks like there may be plans to add it. |
|
No |
|
19.Maintenance |
|
|
|
|
Hard to tell. |
There is an email list devoted to the product so it may be possible to get help that way. |
|
Nothing mentioned. |
|
* ToudDoux, while a cool application, is more akin
to MS-Project than it is a user-based bug tracking/request
tool... It is not web-enabled, so its usefullness to us
kind of declines...
* Roundup is still very much in beta
* ProManager is definately still in development stage, with lack
of niceties like email notification, but it works, and it also supports
seemingly several dozen languages. It also has strange features like
heiarchical/recursive tasks
* ReqNG: Seems to be down! Is anyone still supporting this?
* GNATS itself is a unix based issue tracking system
that is difficult to train users on. GNATSweb is the
web interface, but it's development is hinged on the
development of GNATS itself. It seems that the
queries can get rather sophisticated if you put in the
learning time...
* OpenTicket evaluationProduct no longer available.
* HelpDesk I would not recommend this product based on what I've seen,
so we can just leave it off the list.
* Open track:This version of OpenTrack uses the SleepyCat database package for storing all PR(problem tracking)s. If you want to use this package commercially, then you should buy a license. Has both TCL and Web interfaces. Source is available but oddly packaged.OpenTrack V4.0 is based upon Tcl8.1. For a commercial, fully supported version of OpenTrack, please see the folks at For a commercial, fully supported version of OpenTrack, please see the folks at AccuRev.Inc.
* ScarabCurrently, the project is pre-alpha: the database schema is being defined, and a GUI mockup has been created. To be implemented as Java servlets.
* Frontdesk: People e-mail their messages into a threaded central repository which may be accessed via the web. Not integrated with a database. Write all tasks into a file.
* WHUPS: still under development. No code yet .. pre-alpha.
flat file database: a relatively simple database system in which each database is contained in a single table. In contrast, relational database systems can use multiple tables to store information, and each table can have a different record format.
top of page
|