[rt-users] Changing the lifecycles __maps__
Landon
landonstewart at gmail.com
Mon Jun 24 16:59:19 EDT 2013
Hello,
What we've done so far is taken a database dump of an existing RT instance
and created a new RT instance with it. The new RT instance was then
upgraded to RT 4 and RTIR was implemented on top of it. All the tickets
that did not belong to one of 4 queues were deleted and the following
remain:
4 old queues with tickets in them
4 new queues (Incident Reports, Incidents, Investigations, Blocks)
To move tickets from one of the old 4 queues we must define a lifecycle
__maps__ to define how the statuses are to be mapped.
My question is about the configuration of these maps… Does one have to
write out the entire LifeCycles configuration and include a few changes or
can one simply add to the current defaults by just writing out the new
values?
Would this be acceptable as a new configuration?
Set(%Lifecycles
__maps__ => {
'from SC-ABUS -> to Incident Reports' => {
'open' => 'open',
'resolved' => 'resolved',
'new' => 'new',
'stalled' => 'stalled',
'deleted' => 'rejected'
} );
*or* is there some easier way even still for all of the existing queues to
have tickets moved to "Incident Reports" and retain the proper status?
--
Landon Stewart <LandonStewart at Gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20130624/d4d99cc5/attachment.htm>
More information about the rt-users
mailing list