Well, there are a couple different answers to this:
1. There has been work done by a user to move the list of possible
statuses into the database. I'm not sure I've ever seen it. At this
late date in RT1's life cycle, I'd be unlikely to make a change
like this that would require users to futz with their database schema
as part of an upgrade.
2. RT2 currently doesn't let you futz with the list of statuses.
However, it _does_ let you define arbitrary keyword selects for use
with each (or every) queue.
-jOn Sat, Jan 20, 2001 at 03:12:29PM +1300, David Hawke wrote:
I am a fairly new user of RT and am finding it pretty much on target.
Having said that, I find the status values a little limiting for the way we want
to track. For example, we’d like to add
- works4me (everytime, of course :-)) )
Having poked my way though the code and modified in a couple of places, I had the
right thing happening in a couple of places, but hadn’t worked through all of the
interrelationships - and then found 1.06, and then 1.07 came along and …
Given that mySQL is in the background, would it be feasible to put the status
values, and potentially the interaction of status and form, into a table. This
would save superficial changes from having to be repeated at each revision of the
David Hawke Ph: +64-9-624 2242
mailto:email@example.com (Home) Fax: +64-9-624 2236
mailto:HawkeD@conwag.com (Work) Mob: 0-21-995 773
Rt-devel mailing list
jesse reed vincent – firstname.lastname@example.org – email@example.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
…realized that the entire structure of the net could be changed to be made
more efficient, elegant, and spontaneously make more money for everyone
involved. It’s a marvelously simple diagram, but this form doesn’t have a way
for me to draw it. It’ll wait. -Adam Hirsch