[rt-users] Copy Multiple value CF to the child ticket

[Ahmed, Mohammed Naweed (LNG-BCT)]

I am using version 3.8.4 so CustomFieldValuesAsString is not available.

I changed the template like this:
CustomField-n: {
             my $separator = "\n";
             my $CFValue = $Tickets{'TOP'}->CustomFieldValues(n);
             return join ($separator, grep { defined $_ }
                          map { $_->Content }
@{$CFValue->ItemsArrayRef});
               }

To get the values as strings but it still not working, Am I doing
something wrong or is there any extension available for
'CustomFieldValuesAsString' method?


Thanks
N Ahmed



-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin
Falcone
Sent: Tuesday, January 04, 2011 5:03 PM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Copy Multiple value CF to the child ticket

On Tue, Jan 04, 2011 at 03:19:45PM -0500, Ahmed, Mohammed Naweed
(LNG-BCT) wrote:
>    I am creating a child ticket with some of the custom fields
populated from the parent ticket.
>    I know that we can copy the values of the parent CF to the child CF
by:
> 
> 
> 
>     CustomField-n: {$Tickets{'TOP'}->FirstCustomFieldValue('CF Name')}
> 
> 
> 
>    But, how to copy multiple-value CF to the child ticket? The above
code is just populating the
>    first selected value.

Given a new enough RT, CustomFieldValuesAsString will work

-kevin

-----------------------------------------
The information contained in this e-mail message is intended only
for the personal and confidential use of the recipient(s) named
above. This message may be an attorney-client communication and/or
work product and as such is privileged and confidential. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and
that any review, dissemination, distribution, or copying of this
message is strictly prohibited. If you have received this
communication in error, please notify us immediately by e-mail, and
delete the original message.