Hi,
I'd have to agree that the amount of flexibility is what got us to work
with RT.
By default you get a framework, which is rather basic (ticket id, priority,
owner and requestor, etc.). From there you can develop lifecycles (sounds
complicated, but it's a simple config) which you can dedicate
Mark,
I haven't worked with the tools you mentioned, but I can tell you that RT
is designed and written to be very flexible. Rather than design a bunch of
stuff that has to be ripped out or re-worked, Best Practical gives you a
system that acts as a foundation from which you can EASILY add more
As part of a report I'm putting together for our management, I'd
appreciate comments from other RT users as to why you chose RT over
other ticketing systems. In particular, I'm interested to know what
features/benefits RT provides you as compared with other open source
ticketing systems such
