Closed
Bug 214622
Opened 21 years ago
Closed 21 years ago
Bugzilla should avoid multiple sumissions of the same bug.
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Bugzilla
Creating/Changing Bugs
Tracking
()
People
(Reporter: jhmelman, Assigned: myk)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 This bug differ from bug 212191 and bug 145588 because it suggests a simple solution for what I call "stupid dupes". Reproducible: Always Steps to Reproduce: 1.Compose a new bug 2.Click submit bug report 10^^70 times DON'T DO THIS!!! :) Actual Results: 10^^70 incarnations of the same bug now exist. Expected Results: 2nd to 10^^70th incarnations should be ignored This is what I call "stupid dupes": multiple submissions when some problem occur (bug 10163, bug 10164, bug 10165, bug 10166, bug 10167 - read bug 10167, comment #2) or when the user is so used to double-click everything clickable (which seems to be the case of more recent bugs bug 214404, bug 214405 and bug 214453 and bug 214454). A simple solution comes to my mind: store the last N reports in memory, (or just a signature of the last N messages), check the new submission against the ones stored in memory and drop it if it matches any of the previous submissions. N should be large enough in order to avoid this case: user A posts bug blah; user B posts bug bleh; user ... posts bug ...; user A posts bug blah; etc.
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 22353 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•21 years ago
|
||
The first two bug mentioned in the report are more likely dupes of bug 22353 than this one. As I said, it's not about searching the database looking for keywords so that an user recognizes his bug as a would-be dupe, it's about avoiding an EXACT MATCH of one of the last bugs. If Bugzilla personnel finds it is the same case of bug 22353, I'll happily post relevant information to that bug.
Updated•11 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•