Re: [rt-users] Using non-standard status only

2012-09-20 Thread Kenneth Crocker
Kevin, Yep, forgot about that. Been working mostly on 3.6 and 3.8 systems lately. Brain fart. Kenn On Fri, Sep 14, 2012 at 10:47 AM, Kevin Falcone falc...@bestpractical.comwrote: On Wed, Sep 12, 2012 at 09:53:23PM -0700, Kenneth Crocker wrote: Although you could change those status

Re: [rt-users] Using non-standard status only

2012-09-14 Thread Kevin Falcone
On Wed, Sep 12, 2012 at 09:53:23PM -0700, Kenneth Crocker wrote: Although you could change those status values, why? If a ticket is invoiced or whatever, it is still open. Why not create a Custom Field that shows what its state within the open status, ie. invoiced, check pending

[rt-users] Using non-standard status only

2012-09-12 Thread Maciej Dobrzanski
Hello, I want to use custom lifecycles for various queues. The thing I've been wondering about is about some of the standard statuses such as 'new' or 'open'. They are referred to in a few other places besides just tickets: defaults = { on_create = 'new', on_merge

Re: [rt-users] Using non-standard status only

2012-09-12 Thread Thomas Sibley
On 09/12/2012 12:57 AM, Maciej Dobrzanski wrote: I want to use custom lifecycles for various queues. The thing I've been wondering about is about some of the standard statuses such as 'new' or 'open'. They are referred to in a few other places besides just tickets: defaults = {

Re: [rt-users] Using non-standard status only

2012-09-12 Thread Kenneth Crocker
Maciej, Although you could change those status values, why? If a ticket is invoiced or whatever, it is still open. Why not create a Custom Field that shows what its state within the open status, ie. invoiced, check pending and a ton of others. This CF could also be used in queries, dashboards,