On Tue, Jul 19, 2011 at 1:20 PM, Nico Kadel-Garcia <nka...@gmail.com> wrote: > On Tue, Jul 19, 2011 at 12:59 PM, Johan Beisser <j...@caustic.org> wrote:
> It takes significant, thoughtful re-organizaton and a saner workflow. Yes. It's non-trivial to make that happen as a default. > What would be considered to "not suck"? Stability? Security? > Flexibility? Reliable database on the back end? Ease of email > submissions for newbs? RT's stability is fine. It's a webapp with a database back end, and the database is occasionally less than happy. Not a huge problem, sine I can just bounce the DB if need be (it's MySQL, many problems are fixed fairly quickly that way, I've learned). For what it is, it works decently. It's flexible enough to work for use in tracking trouble tickets, but it's been painful enough to upgrade that I hesitate to run a newer version. Even if that newer version might fix some of my UI issues. To make it not suck: - easy to extend, modify, or add in plugins for new features (no patching, please) - simple database schema, no dumping required to upgrade - functional search - merging of tickets - automatically scheduled repeating tickets (heh) - ability to make API calls to the ticket software (i sometimes want to open/list/etc tickets remotely, without using the webt interface directly) You get the idea.
