Duplicate bug reports considered harmful … really?

By Nicolas Bettenburg, Rahul Premraj, Thomas Zimmermann, Sunghun Kim. 2008 IEEE International Conference on Software Maintenance, 2008

296 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Towards more accurate retrieval of duplicate bug reports (2011, background): “In this study, we focus on the second approach for the following reasons.”
Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports (2012, background): “Many researchers mine bug report information to solve software engineering problems such as duplicate bug detection [33, 35], automatic bug triage [4, 7], bug report quality analysis [6, 7], and defect prediction [20, 37].”
What Makes a Good Bug Report? (2008, background): “In other work, we quantified the amount of additional information in bug duplicates [ 6 ] and gave recommendations on how to improve existing bug tracking systems [17].”
Improving bug triage with bug tossing graphs (2009, methodology): “To evaluate our approach, we use the bug triage benchmark (fold 10 of the master set) used by Bettenburg et al. [ 5 ] and two machine learning algorithms, Naive Bayes and Bayesian Networks [2].”