Hi!
Thats not a big thing, if you read and follow the instructions at
http://requesttracker.wikia.com/wiki/Reminders
http://requesttracker.wikia.com/wiki/RemindersThis is working for me like a charm!
I do not RT::Condition::BeforeDue available for 4.0.17, which is the
version I am running.https://www.bestpractical.com/docs/rt/4.0.17/RT/Condition/BeforeDue.html
shows not found.
Actually RT::Condition::BeforeDue worked perfect.
I am using it like this
/opt/rt4/bin/rt-crontool --search RT::Search::FromSQL --search-arg ‘(
Status != “resolved” AND Status != “rejected” AND Queue = “IPHandover” )’
–condition RT::Condition::BeforeDue --condition-arg 48h --action
RT::Action::NotifyGroup --action-arg ‘asif@example.net’ --transaction last
–template ‘Due Soon’
I am using a global template ‘Due Soon’
The ticket {$Ticket->id} is Due in 48 hours. Get busy.
Does the RT::Action::NotifyGroup take User Defined Group as action
argument? I do not want to use action arg Owner, since it will not alert
about
unowned tickets.
Thanks
Greetings,
Markus
RT Training - Boston, September 9-10
http://bestpractical.com/training–
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?