The release notes for 2.0.9 say:
- Abstracted out status enumeration and validation. Sites can now
modify the set of statuses available. Though that’s 100% unsupported.
How do I do that?
matthew zeier - “In mathematics you don’t understand things. You just
get used to them.” - John von Newmann
There’s an array defined in lib/RT/Queue.pm. But it’s really really
unsupported. It’s the first part of some work I was doing for a client who
ended up not paying
-jOn Thu, Nov 22, 2001 at 10:18:44AM -0800, matthew zeier wrote:
The release notes for 2.0.9 say:
- Abstracted out status enumeration and validation. Sites can now
modify the set of statuses available. Though that’s 100% unsupported.
How do I do that?
–
matthew zeier - “In mathematics you don’t understand things. You just
get used to them.” - John von Newmann
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.
There’s an array defined in lib/RT/Queue.pm. But it’s really really
unsupported. It’s the first part of some work I was doing for a client
who
ended up not paying
Just add to
@STATUS = qw(new open stalled resolved dead);
?
Yeah. but I still don’t recommend it ;)On Thu, Nov 22, 2001 at 06:35:21PM -0800, matthew zeier wrote:
There’s an array defined in lib/RT/Queue.pm. But it’s really really
unsupported. It’s the first part of some work I was doing for a client
who
ended up not paying
Just add to
@STATUS = qw(new open stalled resolved dead);
?
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.