Automated duplicate detection for bug tracking systems

By Nicholas Jalbert, Westley Weimer. Dependable Systems and Networks, 2008

302 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.

What Makes a Good Bug Report? (2008, background): “Several studies used bug reports to automatically assign developers to bug reports [4], [5], [20], assign locations to bug reports [19], track features over time [26], recognize bug duplicates [22], [29], [32], [54], [60], assess the severity [44], predict effort for bug reports [63], identify bug t”
RCLinker: Automated Linking of Issue Reports and Commits Leveraging Rich Contextual Information (2015, unknown): “There also a number of techniques that infer missing links between duplicated bug reports [52], [59], [26], [55], [54], [58], [48], [1].”
A discriminative model approach for accurate duplicate bug report retrieval (2010, methodology): “The ﬁrst one is automatically ﬁltering duplicates to prevent multiple duplicate reports from reaching triagers [11].”
Towards more accurate retrieval of duplicate bug reports (2011, background): “This process however is not scalable for systems with large user base as the process could take much time.”