At Thursday 5/11/2006 03:52 AM, David Di wrote:
I encountered a strange problem when setting value for a custom
field. If anyone can give me a lead that will be appreciated.
Note: this action is to set current transaction user to be the
Evaluator, fill in his real name instead of RT id.
History record in the ticket:
RT_System - Evaluator James Wot added
wotj01 - Evaluator James Wot deleted
Note: first line shows that the scrip updated the CF:Evaluator
successfully but then there's another transaction shows that the
user deleted the CF's value. But the user didn't do that. So it must
be some internal mechanism did that.
Hello David,
You didn't describe what the user-defined condition does, but I can
guess what's happening. I'm assuming that the problem occurs when a
ticket is updated in the web interface, from a screen that allows
custom fields to be updated.
When you submit the form, the CF value on the screen is blank. The
scrip changes the value to 'James Wot'. Then the values submitted
from the form are processed - RT sees that the current CF value is
'James Wot' and that the submitted value is null. It interprets this
as a deletion.
Steve
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
We're hiring! Come hack Perl for Best Practical:
http://bestpractical.com/about/jobs.html
