Ask HN: Support ticketing system
Hello HN'ers,
I'm in the market for a new support ticketing system.
So far we've been using a todo list on steroids, and it has served us well, but we need more features that this one does not contain, so the time has come to upgrade.
The biggest missing feature is good email integration, so whatever will replace this should at least do that well, furthermore we have a ton of stuff on the go, development in several branches with a beta environment for each of them.
What kind of ticketing system would you recommend ?
Which ones would you definitely stay away from ?
(
22 comments
| 18 points
| on HN
)
Both of these platforms have great API's and good email integration and they are both highly recommended.
If there is one I would absolutely stay away from, it would be Remedy (from BMC software). Remedy, even after all these versions, has one of the worst interfaces I have ever used, and has a lot of illogical limitations.
http://www.bugzilla.org/ http://trac.edgewall.org/
Personally, I don't think that the mode matters as much as consistency in method. I've successfully managed support tickets for smaller projects on a series of google doc spreadsheets without any problems. It makes for easier sharing with the client as well.
Bugzilla might fit your needs best out of the three I know about. Good luck!
ie. user purchases your product, has problem/question, emails [email protected] and the support ticketing system picks up the email, autoresponds, etc.
I think what you're talking about is a bit different... although please do correct me if I'm wrong.
I believe it is PHP-based as well, if that matters.
The price is pretty good though - ~$500 for an 'owned' license (http://www.kayako.com/purchasing/pricing.php).
All that said, I'm interested to see what other options people suggest.
http://www.kayako.com/trial/license.php
I used Trac briefly about four years ago and liked it, but it was a bit of a bear to install. On the other hand, you spend the majority of your time using a system, not installing it. Once installed it was fine. I liked the front-end to Subversion a lot, and the integrated wiki was a huge plus. It's written in Python, but there was a time when the Ruby developers used it, although they moved to Redmine a while ago.
I hear good things about Redmine. Sounds like Trac, but improved. I'm planning on experimenting with it.
We used Basecamp a couple of years ago to plan a major overhaul of our flagship web site, and it was a good fit. But we maintain the web site with FogBugz, which we feel is a better fit for development and maintenance as opposed to project planning.
I would no longer choose to work with any sort of tracking system that didn't have an integrated wiki that gave you easy cross-linking between wiki pages and cases or tickets.
http://www.redmine.org/
I would suggest looking at RT: Request Tracker. It has excellent support for creating and managing tickets with email.