Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Quality of bug reports in Eclipse
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange
Extracting structural information from bug reports
Proceedings of the 2008 international working conference on Mining software repositories
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Improving bug triage with bug tossing graphs
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
IEEE Transactions on Software Engineering
Fine-grained incremental learning and multi-feature tossing graphs to improve bug triaging
ICSM '10 Proceedings of the 2010 IEEE International Conference on Software Maintenance
"Not my bug!" and other reasons for software bug report reassignments
Proceedings of the ACM 2011 conference on Computer supported cooperative work
| Hi-index | 0.00 |
Bug reports in widely used defect tracking systems contains standard and mandatory fields like product name, component name, version number and operating system. Such fields provide important information required by developers during bug fixing. Previous research shows that bug reporters often assign incorrect values for such fields which cause problems and delays in bug fixing. We conduct an empirical study on the issue of incorrect component assignments or component reassignments in bug reports. We perform a case study on open-source Eclipse and Mozilla projects and report results on various aspects such as the percentage of reassignments, distribution across number of assignments until closure of a bug and time difference between creation and reassignment event. We perform a series of experiments using a machine learning framework for two prediction tasks: categorizing a given bug report into a pre-defined list of components and predicting whether a given bug report will be reassigned. Experimental results demonstrate correlation between terms present in bug reports (textual documents) and components which can be used as linguistic indicators for the task of component prediction. We study component reassignment graphs and reassignment probabilities and investigate their usefulness for the task of component reassignment prediction.