[rt-users] Request for comments: Configurable Status

[Jesse]

In the traditional RT model, the "Status" field is a simple, limited
list of possible states that a ticket can be in. Roughly: untouched,
active, temporarily inactive, permanently inactive.  For more advanced
workflow, we've recommended that users create custom fields or use
multiple queues to represent different workflow stages.  Of late,
there's been an upswing in the number of users who would rather simply
modify the existing "status" field. 

Would a simple editable per-queue ordered list of possible statuses
(stati?) be sufficient for your needs?  Do you need to control which
status transitions are allowed? Do you need to be able to lock down
certain statuses such that they're only selectable by specific users?


	Best,
	Jesse


--