Just to double check, you commented out line 954, or something else?
Thanks,
Armin
From: Aaron McCormack [mailto:aa...@backblaze.com]
Sent: Monday, June 22, 2015 4:58 PM
To: Armin Liedtke
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Can't call method warn for
On Wed, Jun 17, 2015 at 12:57 PM, Daniel Moore daniel.mo...@osbornewood.com
wrote:
Hello,
Is there anyway to take the comment directly out of lifecycle for the
Tickets?
Yep.
https://bestpractical.com/docs/rt/latest/customizing/lifecycles.html
You can copy the default lifecycle from
Sorry I wasn't clear...
Yes, just the logging on line 954 so that it reads:
#RT-Logger-$loglevel($msg);
This isn't a proper solution, but is working for me temporarily.
Aaron
On Jun 23, 2015, at 8:36 AM, Armin Liedtke armha...@uw.edu wrote:
Just to double check, you commented out line
While I don't have a complete list of transaction types for you, I do have a
scrip that will write relevant transaction/ticket info to the logs.
Condition: On transaction
Action: User Defined
Template: Blank
Stage: TransactionCreate
Custom Action Prep Code:
$RT::Logger-debug( TRANSACTION TYPE:
Where can I find a list of transaction types?
I found http://requesttracker.wikia.com/wiki/Transaction, but that appears
to be old or incomplete (for example, it doesn't include SetWatcher).
Thanks,
Keith
On 17 Jun 2015, at 13:57, Daniel Moore wrote:
Hello,
Is there anyway to take the comment directly out of lifecycle for
the Tickets? I have been able to rename some things but we do not want
users commenting on Tickets since the default behavior for a comment
is to not reply or send emails
