Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Information needs in bug reports: improving cooperation between developers and users
Proceedings of the 2010 ACM conference on Computer supported cooperative work
Characterizing and predicting which bugs get fixed: an empirical study of Microsoft Windows
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
The missing links: bugs and bug-fix commits
Proceedings of the eighteenth ACM SIGSOFT international symposium on Foundations of software engineering
"Not my bug!" and other reasons for software bug report reassignments
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Proceedings of the 34th International Conference on Software Engineering
Juggling the Jigsaw: towards automated problem inference from network trouble tickets
nsdi'13 Proceedings of the 10th USENIX conference on Networked Systems Design and Implementation
PorchLight: a tag-based approach to bug triaging
Proceedings of the 2013 International Conference on Software Engineering
Situational awareness: personalizing issue tracking systems
Proceedings of the 2013 International Conference on Software Engineering
Informing development decisions: from data to information
Proceedings of the 2013 International Conference on Software Engineering
Search-based duplicate defect detection: an industrial experience
Proceedings of the 10th Working Conference on Mining Software Repositories
A contextual approach towards more accurate duplicate bug report detection
Proceedings of the 10th Working Conference on Mining Software Repositories
Hi-index | 0.01 |
Developers typically rely on the information submitted by end-users to resolve bugs. We conducted a survey on information needs and commonly faced problems with bug reporting among several hundred developers and users of the APACHE, ECLIPSE and MOZILLA projects. In this paper, we present the results of a card sort on the 175 comments sent back to us by the responders of the survey. The card sort revealed several hurdles involved in reporting and resolving bugs, which we present in a collection of recommendations for the design of new bug tracking systems. Such systems could provide contextual assistance, reminders to add information, and most important, assistance to collect and report crucial information to developers.