Closed
Bug 295213
Opened 20 years ago
Closed 20 years ago
whine mail still goes out even though whinedays = "0"
Categories
(Bugzilla :: Whining, defect)
Bugzilla
Whining
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: gabriel_hernandez, Assigned: Wurblzap)
Details
Attachments
(2 files)
|
1.21 KB,
patch
|
LpSolit
:
review+
|
Details | Diff | Splinter Review |
|
1.26 KB,
patch
|
LpSolit
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Build Identifier: Bugzilla 2.18 We have currently enabled the whine mail feature in our internal installation of Bugzilla 2.18. According to the parameters documentation (here: http://www.bugzilla.org/docs/2.18/html/parameters.html), I should be able to disable the "whining" at will through the parameters page by setting the whinedays value to "0". When set to "0" (without the quotes), the whine mails are sent out on a daily basis. Is this an error in the documentation or should the whineatnews.pl script be updated? Thanks in advance for any help. Reproducible: Always Steps to Reproduce: 1.Enable a cron tab entry for whineatnews.pl on a daily schedule 2.Set the whine days value on the parameters page to "0" (no quotes) Actual Results: Whining still sends out on a daily basis. Expected Results: whineatnews.pl should end with no action if whinedays is "0"
| Assignee | ||
Comment 1•20 years ago
|
||
The description of the whinedays parameter says "The number of days that we'll let a bug sit untouched in a NEW state before our cronjob will whine at the owner". So -- if you set it to 0, it'll let a bug sit 0 days in a NEW state before the cronjob whines at the owner. As a result, it'll whine every cron run (i.e. probably daily). If you want to effectively disable whining, set the parameter to a very high value.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Assignee | ||
Comment 2•20 years ago
|
||
Reopening -- sorry, you're talking about docs while I looked at the parameter description. Docs should be consistent with behaviour. I'm fine with either changing docs or code -- both sounds sensible to me.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
| Assignee | ||
Comment 3•20 years ago
|
||
| Assignee | ||
Comment 4•20 years ago
|
||
Attachment #184310 -
Flags: review?
| Assignee | ||
Updated•20 years ago
|
Severity: normal → minor
OS: other → All
Hardware: Other → All
Target Milestone: --- → Bugzilla 2.18
| Reporter | ||
Comment 5•20 years ago
|
||
Thanks for the patches. I will test at the next available opportunity and reply with the results
| Assignee | ||
Updated•20 years ago
|
Flags: blocking2.20?
| Reporter | ||
Comment 6•20 years ago
|
||
We have implanted the attached patches and they work as expected. Thank you, wurblzap.
Comment 7•20 years ago
|
||
Comment on attachment 184309 [details] [diff] [review] HEAD patch r=LpSolit
Attachment #184309 -
Flags: review? → review+
Comment 8•20 years ago
|
||
Comment on attachment 184310 [details] [diff] [review] Branch patch r=LpSolit
Attachment #184310 -
Flags: review? → review+
Updated•20 years ago
|
Flags: approval?
Flags: approval2.18?
Comment 9•20 years ago
|
||
Good low-risk polish fix.
Flags: blocking2.20?
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval+
Comment 10•20 years ago
|
||
Tip: Checking in defparams.pl; /cvsroot/mozilla/webtools/bugzilla/defparams.pl,v <-- defparams.pl new revision: 1.158; previous revision: 1.157 done Checking in whineatnews.pl; /cvsroot/mozilla/webtools/bugzilla/whineatnews.pl,v <-- whineatnews.pl new revision: 1.18; previous revision: 1.17 done 2.18.1: Checking in defparams.pl; /cvsroot/mozilla/webtools/bugzilla/defparams.pl,v <-- defparams.pl new revision: 1.128.2.4; previous revision: 1.128.2.3 done Checking in whineatnews.pl; /cvsroot/mozilla/webtools/bugzilla/whineatnews.pl,v <-- whineatnews.pl new revision: 1.14.2.3; previous revision: 1.14.2.2 done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•