After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 369324 - option for disabling duplicate notifications
option for disabling duplicate notifications
Status: RESOLVED NOTGNOME
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: email
unspecified
Other All
: Normal normal
: Bugzilla 3.0
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks: 389704
 
 
Reported: 2006-11-02 09:53 UTC by Christian Kirbach
Modified: 2009-08-21 06:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Kirbach 2006-11-02 09:53:09 UTC
Currently, there is no option to prevent duplicate messages under email preferences. 
Personally, I consider those notifications as spam. In almost any case I am really not intrested in them and they are no use for me.
Comment 1 Christian Kirbach 2006-11-06 15:54:02 UTC
there seems to be demand for this from various people.
Comment 2 Kai Schroeder 2006-11-09 17:26:39 UTC
I am one of them and I would even prefer this to be the default behaviour.
Comment 3 Elijah Newren 2006-11-09 17:30:39 UTC
I agree that it makes sense as the default behavior; if the duplicate bug report has useful information, bugsquadders already add that info to the original report in an additional comment.
Comment 4 Andrew Sobala 2006-11-10 19:07:18 UTC
Crackpipe time: What about sending out a notification if the rate of duplication exceeds some magic value? That way if hundreds of duplicates start flooding in, you'll still find out about it.
Comment 5 Olav Vitters 2006-11-19 21:11:32 UTC
Would be much easier to do under 3.0. I'll probably make sure it is a standard option in 3.2.
Comment 6 Max Kanat-Alexander 2009-08-21 06:37:48 UTC
This is something that should be done upstream, and I believe there is already a bug filed for it there. (Upstream bugs are tracked at http://bugzilla.mozilla.org/ ).