dwx wrote: > Lately most of my effort in the Mozilla project is killing duplicate bug > reports and RFEs in Bugzilla and newsgroups. However, the list of confirmed > bugs just keep growing, and this is really discouraging. I do not know how > you guys handle what must be a large number of e-messages everyday, but all > I know is I cannot handle even a few of them (it usually takes me some five > minutes to track down a duplicate report). > > I would like to write documentation on handling bug reports and RFEs. This > should off load some stress from the shoulders of the better programmers > (and might accelerate the speed at which documentation become obsolete, > which would be good for everyone except us :p ). However, I will need some > help. > > Minh, your wishlist project is probably doing the same thing. Any help? >
I think that the best way to reduce duplicates is to link/list summaries of bugs together. For example, the summary of bug A is "[RFE]linking and delinking tabs and windows." A duplicate bug (B) has the summary of "docking and undocking windows and tabs." Everyone word each summary differently and that is the reason why duplicates are hard to find to the novice user. So Bugzilla should add a second line to the summary in Bug A that contains the summary from bug B. The is a finite number of permutation of wording. Over time, as Bug A's summary gets longer, it will turn up more positive results in a search. Thus, reducing duplicates. Also, we could make a search mandatory before filing a bug. What do you guys think? -- http://wishlist.mozdev.org - Wishlist FAQ Project Please visit and contribute.
