Thanks everybody for helping me on this issue!
I was finally able to solve my problem on scrips and custom fields values.
As few people had suggested, I just had to enable the batch transaction
stage in the RT_SiteConfig.pm, setting stage "TransactionBatch" for that
one scrip that updates the
This behavior doesn't seem to apply to all fields. I've gotten it to
revert when my scrip modifies Owner and a custom field, but if I modify
Priority it doesn't get undone. I've sent it to rt-bugs.
At 12:48 PM 4/23/2007, Gene LeDuc wrote:
I think I know what is happening. At least this is
I think I know what is happening. At least this is what's happening to me.
When you click the submit button after changing a field in a ticket using
the webui, it seems to run a transaction that compares the displayed field
values after all of the other transactions have run - and then it rese
Hi Silvana,
I've had odd results too with Custom Fields on ticket creation & with
custom Scrips. Two things I've found which have helped.
1) Turning on Batch mode in RT_SiteConfig.pm alleviates some of the
problems of not knowing which scrip will trigger first.
# Enable Batching of Trans
On Apr 23, 2007, at 11:19 AM, [EMAIL PROTECTED] wrote:
I have 2 custom fields created at ticket creation time, and 2
others to be updated whenever one of the other two change value.
This is done by several scrips, 2 running at ticket creation and
the others running when one of the 2 initial
I'm still having problems with scrips modifying some custom field values.
I have 2 custom fields created at ticket creation time, and 2 others to be
updated whenever one of the other two change value. This is done by
several scrips, 2 running at ticket creation and the others running when
one o
