Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
skip to main content
10.1109/MSR.2009.5069491guideproceedingsArticle/Chapter ViewAbstractPublication PagesConference Proceedingsacm-pubtype
Article

Assigning bug reports using a vocabulary-based expertise model of developers

Published: 16 May 2009 Publication History

Abstract

For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment of a report to a developer with the appropriate expertise. In this paper, we present an approach to automatically suggest developers who have the appropriate expertise for handling a bug report. We model developer expertise using the vocabulary found in their source code contributions and compare this vocabulary to the vocabulary of bug reports. We evaluate our approach by comparing the suggested experts to the persons who eventually worked on the bug. Using eight years of Eclipse development as a case study, we achieve 33.6% top-1 precision and 71.0% top-10 recall.

Cited By

View all

Recommendations

Comments

Information & Contributors

Information

Published In

cover image Guide Proceedings
MSR '09: Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
May 2009
212 pages
ISBN:9781424434930

Publisher

IEEE Computer Society

United States

Publication History

Published: 16 May 2009

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 12 Feb 2025

Other Metrics

Citations

Cited By

View all
  • (2023)4Experts: A Task Recommendation Approach Using Machine Learning and Biometric DataProceedings of the XIX Brazilian Symposium on Information Systems10.1145/3592813.3592882(1-8)Online publication date: 29-May-2023
  • (2022)Context- and Fairness-Aware In-Process Crowdworker RecommendationACM Transactions on Software Engineering and Methodology10.1145/348757131:3(1-31)Online publication date: 7-Mar-2022
  • (2022)SPANKnowledge-Based Systems10.1016/j.knosys.2021.107711236:COnline publication date: 25-Jan-2022
  • (2021)Why Some Bug-bounty Vulnerability Reports are Invalid?Proceedings of the 15th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)10.1145/3475716.3484193(1-6)Online publication date: 11-Oct-2021
  • (2021)Fast Outage Analysis of Large-scale Production Clouds with Service Correlation MiningProceedings of the 43rd International Conference on Software Engineering10.1109/ICSE43902.2021.00085(885-896)Online publication date: 22-May-2021
  • (2020)Mining expertise of developers from software repositoriesInternational Journal of Computer Applications in Technology10.1504/ijcat.2020.10658162:3(227-239)Online publication date: 1-Jan-2020
  • (2020)Context-aware in-process crowdworker recommendationProceedings of the ACM/IEEE 42nd International Conference on Software Engineering10.1145/3377811.3380380(1535-1546)Online publication date: 27-Jun-2020
  • (2018)Be careful of when: an empirical study on time-related misuse of issue tracking dataProceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering10.1145/3236024.3236054(307-318)Online publication date: 26-Oct-2018
  • (2018)FEVEREmpirical Software Engineering10.1007/s10664-017-9557-623:2(905-952)Online publication date: 1-Apr-2018
  • (2017)Improving Automated Bug Triaging with Specialized Topic ModelIEEE Transactions on Software Engineering10.1109/TSE.2016.257645443:3(272-297)Online publication date: 1-Mar-2017
  • Show More Cited By

View Options

View options

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media