An Empirical Study of Bug Report Field Reassignment

A bug report contains many fields, such as product, component, severity, priority, fixer, operating system (OS), platform, etc., which provide important information for the bug triaging and fixing process. It is important to make sure that bug information is correct since previous studies showed tha...

Full description

Saved in:
Bibliographic Details
Main Authors: XIA, Xin, LO, David, WEN, Ming, EMAD, Shihab, ZHOU, Bo
Format: text
Language:English
Published: Institutional Knowledge at Singapore Management University 2014
Subjects:
Online Access:https://ink.library.smu.edu.sg/sis_research/2031
https://ink.library.smu.edu.sg/context/sis_research/article/3030/viewcontent/06747167.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
Institution: Singapore Management University
Language: English
id sg-smu-ink.sis_research-3030
record_format dspace
spelling sg-smu-ink.sis_research-30302020-07-22T07:40:27Z An Empirical Study of Bug Report Field Reassignment XIA, Xin LO, David WEN, Ming EMAD, Shihab ZHOU, Bo A bug report contains many fields, such as product, component, severity, priority, fixer, operating system (OS), platform, etc., which provide important information for the bug triaging and fixing process. It is important to make sure that bug information is correct since previous studies showed that the wrong assignment of bug report fields could increase the bug fixing time, and even delay the delivery of the software. In this paper, we perform an empirical study on bug report field reassignments in open-source software projects. To better understand why bug report fields are reassigned, we manually collect 99 recent bug reports that had their fields reassigned and emailed their reporters and developers asking why these fields got reassigned. Then, we perform a large-scale empirical study on 8 types of bug report field reassignments in 4 open-source software projects containing a total of 190,558 bug reports. In particular, we investigate 1) the number of bug reports whose fields get reassigned, 2) the difference in bug fixing time between bug reports whose fields get reassigned and those whose fields are not reassigned, 3) the duration a field in a bug report gets reassigned, 4) the number of fields in a bug report that get reassigned, 5) the number of times a field in a bug report gets reassigned, and 6) whether the experience of bug reporters affect the reassignment of bug report fields. We find that a large number (approximately 80%) of bug reports have their fields reassigned, and the bug reports whose fields get reassigned require more time to be fixed than those without field reassignments. 2014-02-01T08:00:00Z text application/pdf https://ink.library.smu.edu.sg/sis_research/2031 info:doi/10.1109/CSMR-WCRE.2014.6747167 https://ink.library.smu.edu.sg/context/sis_research/article/3030/viewcontent/06747167.pdf http://creativecommons.org/licenses/by-nc-nd/4.0/ Research Collection School Of Computing and Information Systems eng Institutional Knowledge at Singapore Management University Computer Sciences Software Engineering
institution Singapore Management University
building SMU Libraries
continent Asia
country Singapore
Singapore
content_provider SMU Libraries
collection InK@SMU
language English
topic Computer Sciences
Software Engineering
spellingShingle Computer Sciences
Software Engineering
XIA, Xin
LO, David
WEN, Ming
EMAD, Shihab
ZHOU, Bo
An Empirical Study of Bug Report Field Reassignment
description A bug report contains many fields, such as product, component, severity, priority, fixer, operating system (OS), platform, etc., which provide important information for the bug triaging and fixing process. It is important to make sure that bug information is correct since previous studies showed that the wrong assignment of bug report fields could increase the bug fixing time, and even delay the delivery of the software. In this paper, we perform an empirical study on bug report field reassignments in open-source software projects. To better understand why bug report fields are reassigned, we manually collect 99 recent bug reports that had their fields reassigned and emailed their reporters and developers asking why these fields got reassigned. Then, we perform a large-scale empirical study on 8 types of bug report field reassignments in 4 open-source software projects containing a total of 190,558 bug reports. In particular, we investigate 1) the number of bug reports whose fields get reassigned, 2) the difference in bug fixing time between bug reports whose fields get reassigned and those whose fields are not reassigned, 3) the duration a field in a bug report gets reassigned, 4) the number of fields in a bug report that get reassigned, 5) the number of times a field in a bug report gets reassigned, and 6) whether the experience of bug reporters affect the reassignment of bug report fields. We find that a large number (approximately 80%) of bug reports have their fields reassigned, and the bug reports whose fields get reassigned require more time to be fixed than those without field reassignments.
format text
author XIA, Xin
LO, David
WEN, Ming
EMAD, Shihab
ZHOU, Bo
author_facet XIA, Xin
LO, David
WEN, Ming
EMAD, Shihab
ZHOU, Bo
author_sort XIA, Xin
title An Empirical Study of Bug Report Field Reassignment
title_short An Empirical Study of Bug Report Field Reassignment
title_full An Empirical Study of Bug Report Field Reassignment
title_fullStr An Empirical Study of Bug Report Field Reassignment
title_full_unstemmed An Empirical Study of Bug Report Field Reassignment
title_sort empirical study of bug report field reassignment
publisher Institutional Knowledge at Singapore Management University
publishDate 2014
url https://ink.library.smu.edu.sg/sis_research/2031
https://ink.library.smu.edu.sg/context/sis_research/article/3030/viewcontent/06747167.pdf
_version_ 1770571776893386752