Active
Project:
Support Nag
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Mar 2010 at 14:24 UTC
Updated:
9 Jun 2011 at 18:52 UTC
Using Support 6.x-1.2 and Support Nag 6.x-1.x-dev.
In the Support Nag settings, under, "Only apply action to selected state(s):" I have the following selected:
new, action, reviewed, pending
Under, "Only apply action to selected priorities:" I have the following selected:
critical
I should receive Nag email notifications of any critical ticket with a state of new, action, reviewed or pending. I should NOT receive Nag emails if a critical ticket has a state of closed. (In other words, if a ticket is closed I should not receive Nag emails about it.) However, I am receiving Nag emails of critical tickets which have been closed.
Comments
Comment #1
NToronto commentedfriendly bump :-)
Comment #2
downtap commentedI'm finding that nag emails are sent on everything. Receiving blank emails like this:
This is a regular notification for the following open tickets:
[tickets]
I know it's alpha, but I'm trying to avoid hacking it to death if there's some known easy fixes.
Comment #3
NToronto commentedI am experiencing the same issue as downtap.
Comment #4
cbutera commentedSame problem here. Trying to get a daily digest of tickets with new status. But all I get is a blank email with [tickets] (there are no new tickets).
Comment #5
NToronto commentedFriendly bump? Any resolution?
Comment #6
jeremy commentedMarking as a critical bug as currently the module does not work like designed, and clearly this is a blocker before a new version of the module could be released.
Patches are encouraged...
Comment #7
schildi commentedtoken replacement depends on language setting. Possibly it finds not the right language to use.
As far as I know the page language is taken as default.
I don't have this issue but modified the source code a bit. In file support_nag.module (near end of function support_nag_cron) there is now
Does this help anybody?
Comment #8
St.Ego commentedThe problem is that the support_nag_cron() does not stop execution when no tickets are found. I fixed the problem by adding a check on the total $nids found, and to skip mailing if none, starting around line 65 of support_nag.module: