[rt-users] Notify about tickets that are Due in 48 hours

[Asif Iqbal]

On Tue, Sep 16, 2014 at 11:23 AM, Asif Iqbal <vadud3 at gmail.com> wrote:

>
>
> On Mon, Sep 15, 2014 at 1:07 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
>
>>
>>
>> On Mon, Sep 15, 2014 at 6:54 AM, <Markus.Wildbolz at eu.magna.com> wrote:
>>
>>> 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/Reminders>
>>>
>>> This 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 at example.net'  --transaction
> last --template 'Due Soon'
>
>

any idea why I am getting email every hour? I was hoping only get alerted
when it matches 48h and not next hour since it would be due in 47h then.

posted on #rt as well.



> I am using a global template 'Due Soon'
>
> Subject: {$Ticket->id} Ticket Due in 48 hours!
>
> 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?
>
>


-- 
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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140916/e57a1f95/attachment.htm>