[rt-users] Request for comments: Configurable Status

[Dave Dennis]

As the one that inadvertently started this, I wanted to say that I think the
existing RT statuses are fine, IF "Custom Fields" were available throughout RT
and not just on some pages.  This would allow workflow resolve status
customizations to be solved by Custom Fields rather than hardcode server-wide
status changes.

But if there are unforseen issues with that, configurable statuses (per queue)
would be amazing and great, too.

Kind regards,


+-------------------------
+ Dave Dennis
+ Seattle, WA
+ dmd at speakeasy.org
+ http://www.dmdennis.com
+-------------------------

On Wed, 23 Jun 2004, Jesse wrote:

>
> 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
>
>
> --
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> RT Developer and Administrator training is coming to LA, DC and Frankfurt this spring and summer.
> http://bestpractical.com/services/training.html
>
> Sign up early, as class space is limited.
>