The new "ticket lifecycle" state engine... What is it?

I don’t think I’ll have any problem convincing people to upgrade to RT4.0 when it comes out, since management already seeks to have Date custom fields, but I was wondering what the ticket lifecycle state engine, mentioned here[1], is.

[1] - http://blog.bestpractical.com/2010/09/rt-394-first-development-release-leading-to-rt-400.html

Josh Narins

Director of Application Development
SeniorBridge
845 Third Ave
7th Floor
New York, NY 10022
Tel: (212) 994-6194
Fax: (212) 994-4260
Mobile: (917) 488-6248
jnarins@seniorbridge.com
seniorbridge.comhttp://www.seniorbridge.com/

[http://www.seniorbridge.com/images/seniorbridgedisclaimerTAG.gif]

SeniorBridge Statement of Confidentiality: The contents of this email message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. Any dissemination, distribution or copying of this email by an unintended or mistaken recipient is strictly prohibited. In said event, kindly reply to the sender and destroy all entries of this message and any attachments from your system. Thank you.

I don’t think I’ll have any problem convincing people to upgrade to RT4.0 when
it comes out, since management already seeks to have Date custom fields, but I
was wondering what the ticket lifecycle state engine, mentioned here[1], is.

Have a look in etc/RT_Config.pm at the %Lifecycles section