If you copy the default lifecycle section from RT_Config.pm over to your
RT_SiteConfig.pm file, you should have no problems making that change.
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Nehmer Torben
Sent: November-03-11 9:54
I've installed (via cpan) RT::Extension::SpawnLinkedTicketInQueue version 0.05
on RT 4.0.2 and I'm unable to see the added link controls.
I've added the extension to the RT_SiteConfig file, flushed the mason cache and
restarted my webserver (the extension is listed in the configuration.html),
From: Alex Vandiver [mailto:ale...@bestpractical.com]
Sent: Friday, July 22, 2011 10:02 AM
To: Ian Roy
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] Unable to transfer tickets to a queue with a different
lifecycle
On Thu, 2011-07-21 at 20:57 -0600, Ian Roy wrote:
I've made
Hi,
I'm trying to allow ticket transfers between two queues that have modified
lifecycles and I'm running into a snag: There is no mapping for statuses
between these queues. Contact your system administrator.
I've attempted to configure the status mapping in RT_SiteConfig.pm, but I must
be
Your __maps__ is missing one of its two leading underscores, but I
presume that to be a copy-and-paste mistake. The actual problem is your
quoting. You want:
__maps__ = {
'swdev - default' = {
'Created' = 'new',
'InDevelopment' = 'open',
'Completed' =
