|
I wrote my own.
There are good projects out there, but the better they are, the more dead their development is..
Stonekeep was AWESOME but it's pretty much dead..
IspDB was great but seems to be dead.. I wrote mine around this.
Perldesk is nice.
bugzilla is good, but NOT userfriendly at all. it's more work to make a good interface around bugzilla than to write your own.
Resourcetracker is great, but it took me 3 days to get it working properly, and it was still buggy.. anything that takes me more than 4 hours to get working isn't worth my time.
What features do you want out of a trouble ticketing system? When I went searching, here's what I wanted (in order of priority)
1. e-mail based submissions/responses
2. Web based issues/responses
3. Issue tracking & resolving capabilities
4. Statistics on bugs and bug classifcations (and the ability to classify the tickets of course)
5. WAP .. I wanted to see it on my palm and cell phone
6. Open Source (which mine isn't because it's not really mine but a company I work for)
7. Perl or Php. I HATE python.
|