Proposed: the ability to limit a search to just bugs that already have DUPs. Sometimes, while trying to plow through the list of Browser-General bugs for prescreening ( http://www.mozilla.org/quality/browser/prescreening.html ), I will notice that: (a) a bug report is *definitely* a DUP (b) I've seen the bug it should be made a DUP of before, and it already had DUPs (c) searching on the Summary isn't finding (b) Often it turns out that the reason for (c) is that the Summary of the bug report that holds the DUPs (or is the root of a tree of DUPs) has been written or rewritten by an engineer in terms of the work to be done, rather than the symptoms reported. In such a case there is not much to do but search the comments, after limiting the search in other ways as much as is possible. This enhancement would make one more limit possible, making the search faster and more efficient in cases where there are already known DUPs of the same bug. I expect that this would be implemented much the same as the new "Added Comment" checkbox for email: (1) add a new field to the database, set to an integer "0" for all records (2) arrange for it to be incrmented every time that notice of a another bug being marked a DUP is added to the comments section of a bug report (3) hunt through the old bugs once only to increment the field for each existing "has been marked as a duplicate of this bug. ***" string (4) add a control to the Query page. BTW, now that the boolean charts are available, searching for this purpose could be done by ANDing with a match for "has been marked as a duplicate of this bug. ***" in the comments, but that would be a *punishing* lookup, compared to what is proposed here. Also, setting this up would support a potentially good-enough-for-now fix for bug 25693, where a way to automate finding most-frequently-filed bugs is desired.

I fail to understand why you think this is different than what is discussed in bug 25693. Please continue discussion there. *** This bug has been marked as a duplicate of 25693 ***

Ah, the old, "Is a bug report about a symptom or a problem or a fix?" puzzler. You are entirely right that the type of search wanted here would be supported by the same code that supports the type of search wanted in bug 25693.

moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE