Trouble Ticket Systems?

Zen Master Nate asks: "I work for a startup ISP, and part of my job is support. A trouble ticket system would be quite helpful, but all the ones I have found are overpriced and way too complex for our needs. My question is: What trouble ticketing systems do you use, commercial, freeware/open source, or in-house? Also, if I were to write one, what features are needed, which ones are useful, and which are unnecessary? "

Comments

First Ticket :)

[AliasTheRoot]

If you head over to www.php.net, you'll find a number of freeware projects that do stuff like inventory management, trouble ticketing and web based interfaces to mail, etc - you may find something of relevence there.

wreq

[Anonymous Coward]

Wreq is a freeware web-based trouble-ticket tracking system. The url for it is http://www.math.duke.edu/~yu/wreq/ .

Re:wreq

[Hackboy]

I used wreq at my last job. It was used as a site trouble ticket system and we were planning on replacing it with something more powerful, but I left the company before management decided on a new system. Wreq served the company well for a couple of years

Strong points:

• Open source, change it to suit your liking.
• Easy to integrate into other systems
• Simple email interface.
• Fast

Weak points:

• Limited "ownership" of tickets
• No escalation
• Web interface a little confusing.
• Searching capabilites limited

Keystone

[davetza]

We used keystone for a long time and never had any problems with it. It uses php and sql and has a web interface. You can find it at http://www.stonekeep.com/keystone.php3

In fact as far as I'm concerned it works far better than the very very expensive commercial solution we are now being forced to use.

Req might be useful

[noahm]

Here at the College of Computer Science at Northeastern people have developed a package called Req. It is used by our systems department for tracking requests/problem reports from users. I am only familiar with it from an indirect user's point of view, meaning I've never actually seen the tracking interface in action. With a little bit of digging in the FTP site, though, I've found reference to at least web, Tk, and emacs front ends.

The FTP site is ftp://ftp.ccs.neu.edu/pub/sysadmin/. It doesn't seem like CCS is developing it very actively, but on the plus side it is open source.

noah

OpenTicket

[draziw]

Here's another OpenTicket. This one lets you try it over the net.

GNATS -- ugly, yet simple and does the trick

[Paranoid Diatribe]

Give GNATS a try. It seems to be actively maintained, it has various front ends (tk, web, email, command line), it's pretty lean, and it does the trick.

It isn't very pretty, though. I don't know how the setup is, but we use it where I work (large public university), and it works. Our version is a little dated, so there may be some improvements.

I hear that Bugzilla is nice, though I haven't tried it myself.

My < .02 :)

[Roogna]

Well, here at work (company in this case shall remain unnamed, sadly, I'd love to bitch about them;) they use Remedy.
A big expensive commercial trouble ticket package which should never have become a shipping product.
Though supposedly they have the second largest base of users for a software product in the world.
Us, being the Sun admins taking care of the servers for Remedy, have actually had to implement our own trouble ticket/change control system for Remedy. So we've gone with a web based solution for that, which handles our feature set pretty well.
Basically we gather contact info, group info, project info, priority, what the problem is, who found it, etc...
I'm in the process of putting a snazzy interface on it, and actually am also working on a real version at home in my spare time. Figure Remedy gets emense ammounts of money every day for their product, I could do a commercial release of mine for a pitance, and maybe earn a little spare change to actually live off of.