[Rt-devel] configurable option for fields to use when cloning a ticket
Roedel, Mark
MarkRoedel at letu.edu
Wed Jan 21 14:17:52 EST 2009
OK...a first attempt is attached. This patch against the 3.8.2 release
adds a @TicketCloneFields setting to RT_Config.pm (and RT_Config.pm.in)
and modifies Ticket/Create.html to use that value instead of the
hard-coded list of fields when executing a clone.
--
Mark Roedel
Senior Programmer/Analyst - Web Services
LeTourneau University
-----Original Message-----
From: Jesse Vincent [mailto:jesse at bestpractical.com]
Sent: Wednesday, January 21, 2009 10:07 AM
To: Roedel, Mark
Cc: rt-devel at lists.bestpractical.com
Subject: Re: [Rt-devel] configurable option for fields to use when
cloning a ticket
On Wed, Jan 21, 2009 at 10:05:34AM -0600, Roedel, Mark wrote:
> A few of our users have noted that by default when a
> dependent/parent/child ticket is created using the "Create" link in
the
> "Links" section of a ticket, the new ticket inherits among others the
> TimeEstimated and TimeWorked fields from the existing ticket. If your
> manager pays attention to your time spent requests, this can skew the
> numbers!
>
> The list of fields copied into a new ticket appears to be specified in
> line 267 of Ticket/Create.html. Rather than just maintaining our own
> customized list of fields in a local Create.html, I'm wondering what
> everyone would think of making that a configurable option in the
central
> RT config files?
I'd love to review a patch for that.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rt382-patch-letu20090121-1.txt
Url: http://lists.bestpractical.com/pipermail/rt-devel/attachments/20090121/e87d23a2/attachment.txt
More information about the Rt-devel
mailing list