Ruslan Zakirov ruz at bestpractical.com writes:
Hi,
It's known issue with scrips that set custom fields based on other
fields. You workaround it either by not allowing people to change
custom fields you auto set with scrips or by running your scrip in
batch stage.
Some details. RT
Hi,
It's known issue with scrips that set custom fields based on other
fields. You workaround it either by not allowing people to change
custom fields you auto set with scrips or by running your scrip in
batch stage.
Some details. RT processes updates to custom fields one by one from
request
Hello,
I'm relatively new to RT and have been running into this problem for a
few days now. I've looked everywhere and haven't found a clue. The
closest thing I could find was documented in this post:
http://www.mail-archive.com/rt-users@lists.bestpractical.com/msg10037.html
But, I really
On 14 Jun 2012, at 14:48, Matthew W. wrote:
Hello,
I'm relatively new to RT and have been running into this problem for a
few days now. I've looked everywhere and haven't found a clue. The
closest thing I could find was documented in this post:
Matthew,Tim,
Most likely it is.
Kenn
On Thu, Jun 14, 2012 at 6:54 AM, Tim Cutts t...@sanger.ac.uk wrote:
On 14 Jun 2012, at 14:48, Matthew W. wrote:
Hello,
I'm relatively new to RT and have been running into this problem for a
few days now. I've looked everywhere and haven't found
On Thu, Jun 14, 2012 at 9:48 AM, Matthew W. matt.k.w...@gmail.com wrote:
Here's some psuedocode (code not tested and may contain typos, but my
code works just fine as I can see the transactions in the ticket
history):
my $Value = 'some value';
my $CFName = 'customCF';
my $CF-LoadByName(
