| Authors: |
Israel Herraiz
and Daniel M. German
and Jesus M. Gonzalez-Barahona
and Gregorio Robles
|
| URL: |
http://doi.acm.org/10.1145/1370750.1370786 |
| Tags: |
bug
bug-status
eclipse
msr
|
| Abstract: |
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. |
@inproceedings{paper:herraiz:2008,
title = {Towards a simplification of the bug report form in eclipse},
address = {New York, NY, USA},
author = {Israel Herraiz and Daniel M. German and Jesus M. Gonzalez-Barahona and Gregorio Robles},
booktitle = {MSR '08: Proceedings of the 2008 international workshop on Mining software repositories},
pages = {145--148},
publisher = {ACM},
url = {http://doi.acm.org/10.1145/1370750.1370786},
year = {2008},
abstract = {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.},
keywords = {bug bug-status eclipse msr }
}
::