[Rt-users] Custom Statuses

[Kelly F. Hickel]

It depends on the business model using RT.

We have the same issue, support wants "pendingCustomer",
"pendingQAVerification", "pendingRelease", etc (maybe not those names,
but those semantics).  Yes, I can do that with different queues, but
then (for instance), I can't dedicate a queue to a large customer.
Those are just some simple examples, it goes deeper than that.

-- 
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh at mqsoftware.com
 

> -----Original Message-----
> From: Roger B.A. Klorese [mailto:rogerk at queernet.org]
> Sent: Thursday, April 15, 2004 2:56 PM
> To: Dave Dennis
> Cc: Tim Pierce; Best Practical Users
> Subject: Re: [Rt-users] Custom Statuses
> 
> Dave Dennis wrote:
> 
> >Sorry -- see previous mails.
> >
> >Configurable end-game just means, instead of locked into
> >"new/open/stalled/resolved/dead/deleted"
> >
> >you get to put things like
> >
> >"sold" or "sent brochure" or "check cleared" or whatever
> >as either subsets of or replacements for the ubiquitous
> >and not-detailed-enough "resolved" as a ticket end-condition.
> >
> >
> 
> Those don't seem like trouble-ticket issues to me.
> _______________________________________________
> RT-Users mailing list
> RT-Users at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users