Yes it is. In fact, it is the default behaviour. I have 2 custom lifecycles defined in our RT setup.
Define your lifecycle and the corresponding Mapping Between Queues, as described in this link: https://bestpractical.com/docs/rt/latest/customizing/lifecycles.html#Mapping-Between-Queues In the example, there are two lfecycles defined: Default and Orders. The "__maps__" entry maps one state of one queue to the correspondig state in the other. So, when you change from the Default lifecycle to Orders, any "pending" status will become "new", any "processing" will become "open", and so on. In your case, the final state in Default should be mapped to the new final state in YourCustomLifecycle. Don't forget to define the reverse YourCustomLifecycle->Default mappings too, in case you want to revert the lifecycle change. -Pedro Pedro Pereira Núcleo de Infraestruturas e Telecomunicações Departamento de Informática Alameda da Universidade · Cidade Universitária 1649-004 LISBOA · PORTUGAL T. +351 210 443 567 - Ext. 19817 E. [email protected] <mailto:[email protected]> www.ulisboa.pt <http://www.ulisboa.pt/> On 02-07-2014 21:05, Kenroy Bennett wrote: > Hi All, > I have created a Queue to use the default life cycle have > been used it for several months now. > After using it I realized that I will need to create a new life cycle > for tickets in the Queue. Is it possible to change the life cycle in > the Queue and update tickets in their final state that have used the > default life to a final state in the new lifecycle that I have create. > > > Regards, > Kenroy > >
0x9483169C.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
-- RT Training - Boston, September 9-10 http://bestpractical.com/training
