Le 15/10/2014 20:38, fleon a écrit :
I am having issues making your example work.
I created
/opt/rt4/local/html/MyCallbacks//Elements/ShowHistory/SkipTransaction and it
contains the following:
Wrong path, it must be:
Sorry, i mistyped.
The code is definitely executing, because i put a
RT-Logger-error($Transaction-Type); at the beginning of the code. But i
get all transactions shown on the main ticket view!
I even did just a return; on the code to see it exit and it shows the same.
Here is all the output
I made the code work! I got suspicious when i saw that emails from cron came
from user root, id =12. 12??? Isn't the superuser supposed to be id 1?
So i hardcoded 12 into the line:
return unless $Transaction-Creator == 12;
And now it hides those transactions.
I tried substituting the cron job
On Thu, Oct 16, 2014 at 05:13:38AM -0700, fleon wrote:
Can't i use RT::Action:SendEmail instead of RT::Action::Notify to avoid
getting the transaction on the ticket in the first place? That way i could
delete the callback...But i would need SendEmail to be able to read the
ticket information
I found the thread on the list
http://requesttracker.8502.n7.nabble.com/Suppressing-RT-System-itself-entries-in-Ticket-History-td52865.html
that explains that a method to suppress these kind of elements in the ticket
history is to code a callback where you can skip some transactions.
What would
Le 15/10/2014 14:20, fleon a écrit :
I found the thread on the list
http://requesttracker.8502.n7.nabble.com/Suppressing-RT-System-itself-entries-in-Ticket-History-td52865.html
that explains that a method to suppress these kind of elements in the ticket
history is to code a callback where you
I am having issues making your example work.
I created
/opt/rt4/local/html/MyCallbacks//Elements/ShowHistory/SkipTransaction and it
contains the following:
I restarted the webserver ,assigned permissions to the web user and deleted
the mason cache. I don't see any changes on either screen, my
I am having issues when using rt-crontool to send emails
/opt/rt4/bin/rt-crontool --search RT::Search::FromSQL --search-arg '(Status
= open or Status = new)'
--action RT::Action::SendEmail --action-arg Owner --transaction first
--template 'Recordatorio')
Error:
Template parsing error: Can't
If i change --action RT::Action::SendMail to --action
RT::Action::RecordComment then the template gets ignored and a scrip gets
called that uses its own template and then i get mail.
However i don't want to record a comment, i just want mail to get sent,
otherwise the tickets will get swamped
Another change, with another module:
i changed rt-crontool to:
/opt/rt4/bin/rt-crontool --search RT::Search::FromSQL --search-arg Queue =
'apoyo' AND Owner != 'Nobody' AND ( Status = 'open' OR Status = 'new'
) AND Created '1 day ago' --action RT::Action::Notify --action-arg
'Owner' --template
I had to put this on the template:
To:{$Ticket-OwnerObj-EmailAddress}
Otherwise no email would get sent.
However, i would think a better approach is to not have to hardcode the
owner to the template and pass it as a argument to rt-crontool so i can
reuse the template and have other cron jobs
On Tue, Oct 14, 2014 at 07:16:47AM -0700, fleon wrote:
Revisar el ticket #{$Target-Id} y resolver de ser posible.
{RT-Config-Get('WebURL')}Ticket/Display.html?id={$Target-Id}
I understand the error, it doesn't like $Target-Id, i guess it isn't
available at that moment, but that template is
My guess is that my problem was the NotifyActor setting as you say because i
had already tried the example on the Reminders documentation but without
that setting.
The NotifyActor documentation says that RT doesn't notify the person that
does an update, however IMHO cron should be exempted by
Kevin Falcone-2 wrote
This reminder is for ticket #{$Target =
$Ticket-RefersTo-First-TargetObj;$Target-Id}.
BTW i still get Template parsing error: Can't call method TargetObj on an
undefined value at template line 3 with that example so i am keeping just
Ticket-Id to make it work.
--
View
On Tue, Oct 14, 2014 at 11:30:31AM -0700, fleon wrote:
Kevin Falcone-2 wrote
This reminder is for ticket #{$Target =
$Ticket-RefersTo-First-TargetObj;$Target-Id}.
BTW i still get Template parsing error: Can't call method TargetObj on an
undefined value at template line 3 with that example
On Tue, Oct 14, 2014 at 11:22:57AM -0700, fleon wrote:
The NotifyActor documentation says that RT doesn't notify the person that
does an update, however IMHO cron should be exempted by default since you
don't usually run cron jobs in response of events (aren't scrips for that?).
No biggie
I am finding that RT::Action::Notify is recording onto the history of the
ticket. Is there a way to remove this?
I am getting root (RT) - Outgoing email recorded entries everywhere.
--
View this message in context:
17 matches
Mail list logo
