The basic idea behind the “new” status is that if a ticket isn’t being deal
with by anyone yet, it should be marked as “new”.
This is what my intent was when designing it:
When anything other than mail from the requestor happens, the ticket
should pop open.
When a ticket is stalled and mail comes in from the requestor, it
should pop open. no other action should change the status.
This logic should all be in scrips, not in the core, where it is now.
Somewhere around 2.0.5, bugs in a bunch of this got fixed, but I don’t
remember exactly what.
-jOn Wed, Oct 10, 2001 at 05:23:18PM -0400, Ayan R. Kayal wrote:
So I was wondering how the status of a ticket changes based on additions to
the ticket. I’m currently running 2.0.5 (soon to be upgraded), so if any of
this has changed, let me know. Currently, it seems like, hitting "Take"
keeps a ticket in the “new” status. Commenting keeps it “new” as well, as
does replying. It seems like replying should “open” a ticket. Also, it
appears that the default behavior when a “stalled” ticket is replied to by
the requestor is keeping it “stalled.” It seems like that should “open” the
ticket too. Any comments/rebuttals?
rt-users mailing list
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.