Closed
Bug 71559
Opened 23 years ago
Closed 19 years ago
Need QA-contact exclusion field on mail-config
Categories
(Bugzilla :: Email Notifications, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: shaver, Unassigned)
References
Details
To avoid the frequent and painful QA-contact update spam. (I guess we'd need to permit -- nay, force -- people to make those updates without adding a comment, too, but I think that's configurable.)
Updated•23 years ago
|
Target Milestone: --- → Bugzilla 2.16
Comment 1•23 years ago
|
||
I think bug #73173 is a good way of dealing with the comment problem in general. With that, you can avoid an email even when the person is forced to comment (which, I suspect, they are for QA changes, but don't quote me).
Updated•23 years ago
|
Priority: -- → P3
Updated•23 years ago
|
Depends on: emailprefs
Comment 2•23 years ago
|
||
Mass moving to new product Bugzilla...
Assignee: tara → jake
Component: Bugzilla → Email
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → 2.13
Comment 3•23 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 4•22 years ago
|
||
Changing default owner of Email Notifications component to JayPee, a.k.a. J. Paul Reed (preed@sigkill.com). Jake will be offline for a few months.
Assignee: jake → preed
Comment 5•20 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 6•20 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Comment 7•19 years ago
|
||
This is a WONTFIX. (The problem the bug describes is much reduced anyway.) When we rethought the categories for bug 73665, we didn't split this one out. Gerv
Assignee: preed → email-notifications
QA Contact: mattyt-bugzilla → default-qa
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Updated•19 years ago
|
Target Milestone: Bugzilla 2.22 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•