Configurable option for fields to use when cloning a ticket

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?

Mark Roedel
Senior Programmer/Analyst - Web Services
LeTourneau University

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.

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 UniversityFrom: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Wednesday, January 21, 2009 10:07 AM
To: Roedel, Mark
Cc: rt-devel@lists.bestpractical.com
Subject: Re: [Rt-devel] configurable option for fields to use when
cloning a ticket

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.

rt382-patch-letu20090121-1.txt (2.45 KB)

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.

Looks basically ok to me. I’ve asked one of my folks to do a code
review. Any brave users feel like trying this out to see how well it
works for them?


Mark Roedel
Senior Programmer/Analyst - Web Services
LeTourneau University

-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Wednesday, January 21, 2009 10:07 AM
To: Roedel, Mark
Cc: rt-devel@lists.bestpractical.com
Subject: Re: [Rt-devel] configurable option for fields to use when
cloning a ticket

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.

Content-Description: rt382-patch-letu20090121-1.txt