So, I’m wondering what people are using for a trouble ticket system, if anything?
I don’t host a lot of people - mostly friends and famliy - but I want a more centralized location for people to report issues, upgrade requests, questions, etc.
I’m looking at either using ORTS or Flyspray. I installed PHP Support Tickets from the Install Scripts page to work with, but decided that it wasn’t really intuitive enough for what I am looking for.
We’re obviously using Flyspray, and it works OK. The code is pretty clean, but customizing it is still difficult–it’s hard to make stuff disappear from the UI, as it is too complicated, by default. OTRS, to me, is even worse on the complexity front. It’s quite intimidating to use.
I’ve recently developed a fondness for RT lately, though I haven’t found a place to use it yet. Its email handling is absolutely top-notch (while Flyspray only does email notifications, without an additional tool…I’ve read that there is a Perl script to inject issues via email, but I haven’t tried it). We don’t have an installer for it (yet) though. It’s dependency chain is a little bit long, so it’ll probably take a little while to get into the Install Scripts interface. Particularly since none of our customers are using it…I just happen to think it works pretty nicely.
I’d also like to hear what other folks are using and how they like it. We’ve got to do something about our inability to open and manage tickets via email. I somehow thought we could train users to only use the web interface, but I’ve begun getting lots of replies to the notification emails, which takes the remaining interactions out of the ticket system, and makes it much more difficult to support the customer. So, I think I’m now on the side of “ticket trackers must work well with email”.
when small and simpel I use eTicket. It’s very easy to use and sufficient when only having a few customers and admins.
I also like “crafty syntax live help” very much as it can do so much more and has a chat function if you like.
It’s design is really old fashioned so you will want to change that first lol
Of note is that the new version has a different license, so they’ll need to verify that the new distribution terms don’t effect their ability to include it in Virtualmin.
-Eric
Of note is that the new version has a different license, so they'll need to verify that the new distribution terms don't effect their ability to include it in Virtualmin.
We don’t actually distribute most of the scripts we support–they are downloaded at the time of installation, and we don’t touch the source except to configure it. But, if it’s not Open Source, we generally won’t provide an installer for something, unless we’re working directly with the copyright holder (e.g. they want us to offer an installer for their app).
Oh, yeah, as Eric mentioned: For script updates file a ticket. Jamie has a script that notifies him of new versions, but sometimes things change on the website (or the site doesn’t provide a reliable means of detecting new releases), and so a reminder is good.