The Cathedral and the Bazaar
Data Analysis and Graphics Using R: An Example-based Approach (Cambridge Series in Statistical and Probabilistic Mathematics)
An analysis method for improving a bug modification process in open source software development
Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops
IWSM '09 /Mensura '09 Proceedings of the International Conferences on Software Process and Product Measurement
Fault-prone module detection using large-scale text features based on spam filtering
Empirical Software Engineering
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
A time-lag analysis for improving communication among OSS developers
JSAI-isAI'09 Proceedings of the 2009 international conference on New frontiers in artificial intelligence
Attracting the community's many eyes: an exploration of user involvement in issue tracking
Human Aspects of Software Engineering
International Journal of Open Source Software and Processes
Hi-index | 0.00 |
We believe that the bug report form of Eclipse contains too many fields, and that for some fields, there are too many options. In this MSR challenge report, we focus in the case of the severity field. That field contains seven different levels of severity. Some of them seem very similar, and it is hard to distinguish among them. Users assign severity, and developers give priority to the reports depending on their severity. However, if users can not distinguish well among the various severity options, they will probably assign different priorities to bugs that require the same priority. We study the mean time to close bugs reported in Eclipse, and how the severity assigned by users affects this time. The results shows that classifying by time to close, there are less clusters of bugs than levels of severity. We therefore conclude that there is a need to make a simpler bug report form.