[rt-users] RT 3.8.10 is setting a CF value on new ticket creation?

[Kevin Falcone]

On Wed, Aug 10, 2011 at 09:04:59AM -0400, Jeff Blaine wrote:
> On 8/9/2011 5:28 PM, Kevin Falcone wrote:
> >On Tue, Aug 09, 2011 at 02:59:44PM -0400, Jeff Blaine wrote:
> >>I'm confused and can't see that I am doing anything
> >>wrong.  Either I *am* doing something wrong, or there's
> >>a really bizarre bug in 3.8.10.  Surely it's the former.
> >
> >Since you don't say what the condition of the Scrip is, it's hard to
> >know what the TransactionObj actually is, and whether or not it's
> >relevant.
> >
> >But without knowing more about the contents of Transactions and
> >ObjectCustomFieldValues I'd be guessing at problems.
> 
> Not that I think it matters (because disabling this scrip
> still shows Discovery Method being set somewhere at ticket
> creation)... but FWIW
> 
> Condition: On Create

So, this is an On Create scrip, which means:

> $testcf->LoadByName(Queue => $ticket->QueueObj->id, Name =>
> "Discovery Method");
> my $oldv = trim($self->TransactionObj->OldValue());
> my $newv = trim($self->TransactionObj->NewValue());
> $RT::Logger->info("Old value '$oldv' for Discovery Method.  New
> value '$newv'");

That TransactionObj isn't going to be about setting the Custom Field.

Are there other transactions recorded on this ticket, or was the CF
set during the Create transaction?  How are you creating the ticket?

-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110810/e4b1da4b/attachment.sig>