On 8/10/2011 10:08 AM, Kevin Falcone wrote:
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.
Fair enough, but I still see this which means the regexp
was not matched and the CF was not touched:
No Discovery Method set by scrip 13. No matches. Subject
was 'FJHFLFFKLLK' and requestor was '[email protected]'
Are there other transactions recorded on this ticket, or was the CF
set during the Create transaction? How are you creating the ticket?
There are no other transactions on this ticket.
The ticket history is 1 item (the original message content).
All of our tickets are created via email.
--------
RT Training Sessions (http://bestpractical.com/services/training.html)
* Chicago, IL, USA September 26 & 27, 2011
* San Francisco, CA, USA October 18 & 19, 2011
* Washington DC, USA October 31 & November 1, 2011
* Melbourne VIC, Australia November 28 & 29, 2011
* Barcelona, Spain November 28 & 29, 2011
