Automatic bug triage using text categorization
By Davor Cubranic, Gail C. Murphy. International Conference on Software Engineering and Knowledge Engineering, 2004
473 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/169bb50e92c1a5feb756295e4a9e5492e79cf382
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Sunghun Kim
- Kim Herzig
- David Lo
- Chengnian Sun
- Thomas Zimmermann
- Gaeul Jeong
- Andreas Zeller
- Nicolas Bettenburg
Citations in the corpus
- A discriminative model approach for accurate duplicate bug report retrieval (2010, background): “Anvik et al. [1] and Cubranic and Murphy [8] and Lucca [9] all proposed semi-automatic techniques to categorize bug reports.”
- Automated severity assessment of software defect reports (2008, methodology): “Closer to our work, in as much as some prediction is being made based on observed rules, are the approaches that use the textual similarity between bug descriptions to assign bugs to developers [1, 4, 8, 10].”
- Improving bug triage with bug tossing graphs (2009, methodology): “To assign developers to bug reports, again several approaches used natural language processing [3, 5, 10, 13], however only with moderate success, about 5060% accuracy.”
- Automated duplicate detection for bug tracking systems (2008, background): “Bug report #344134 was submitted on July 10, 2006 and includes the description, “I got a software update of Minefield, but it failed and I got in an endless loop.””
- It's not a bug, it's a feature: How misclassification impacts bug prediction (2013, methodology): “But bug fixes have also been used to estimate development efforts [19], [20], [21], [22], bug triage [23], [24] or automatic bug assignment [25], [26].”
- Predicting the severity of a reported bug (2010, methodology): “Text mining techniques have been previously applied on these descriptions of bug reports to automate the bug triaging process [1, 2, 3] and to detect duplicate bug reports [4, 5].”
- Towards more accurate retrieval of duplicate bug reports (2011, methodology): “[15], Cubranic and Murphy [16], Pordguski et al [17], and Francis et al.”
- Duplicate bug reports considered harmful … really? (2008, methodology): “We also found evidence that information from bug duplicates can improve existing techniques to automatically assign developers to bug reports [2, 7, 8].”
- How Long Will It Take to Fix This Bug? (2007, methodology): “Other bug triaging approaches include a Na¨ive Bayes approach by .c and Murphy [5] and a probabilistic Cubrani´text similarity approach by Canfora and Cerulo [4].”