Automatic Fine-Grained Issue Report Reclassification

Issue tracking systems are valuable resources during software maintenance activities. These systems contain different categories of issue reports such as bug, request for improvement (RFE), documentation, refactoring, task etc. While logging issue reports into a tracking system, reporters can indica...

Full description

Saved in:
Bibliographic Details
Main Authors: Kochhar, Pavneet Singh, Thung, Ferdian, LO, David
Format: text
Language:English
Published: Institutional Knowledge at Singapore Management University 2014
Subjects:
Online Access:https://ink.library.smu.edu.sg/sis_research/2439
https://ink.library.smu.edu.sg/context/sis_research/article/3439/viewcontent/iceccs15_reclassification.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-3439
record_format dspace
spelling sg-smu-ink.sis_research-34392020-12-07T06:52:15Z Automatic Fine-Grained Issue Report Reclassification Kochhar, Pavneet Singh Thung, Ferdian LO, David Issue tracking systems are valuable resources during software maintenance activities. These systems contain different categories of issue reports such as bug, request for improvement (RFE), documentation, refactoring, task etc. While logging issue reports into a tracking system, reporters can indicate the category of the reports. Herzig et al. Recently reported that more than 40% of issue reports are given wrong categories in issue tracking systems. Among issue reports that are marked as bugs, more than 30% of them are not bug reports. The misclassification of issue reports can adversely affects developers as they then need to manually identify the categories of various issue reports. To address this problem, in this paper we propose an automated technique that reclassifies an issue report into an appropriate category. Our approach extracts various feature values from a bug report and predicts if a bug report needs to be reclassified and its reclassified category. We have evaluated our approach to reclassify more than 7,000 bug reports from HTTP Client, Jackrabbit, Lucene-Java, Rhino, and Tomcat 5 into 1 out of 13 categories. Our experiments show that we can achieve a weighted precision, recall, and F1 (F-measure) score in the ranges of 0.58-0.71, 0.61-0.72, and 0.57-0.71 respectively. In terms of F1, which is the harmonic mean of precision and recall, our approach can substantially outperform several baselines by 28.88%-416.66%. 2014-08-01T07:00:00Z text application/pdf https://ink.library.smu.edu.sg/sis_research/2439 info:doi/10.1109/ICECCS.2014.25 https://ink.library.smu.edu.sg/context/sis_research/article/3439/viewcontent/iceccs15_reclassification.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 Fine-Grained Issue Reports Reclassification Software Engineering
institution Singapore Management University
building SMU Libraries
continent Asia
country Singapore
Singapore
content_provider SMU Libraries
collection InK@SMU
language English
topic Fine-Grained
Issue Reports
Reclassification
Software Engineering
spellingShingle Fine-Grained
Issue Reports
Reclassification
Software Engineering
Kochhar, Pavneet Singh
Thung, Ferdian
LO, David
Automatic Fine-Grained Issue Report Reclassification
description Issue tracking systems are valuable resources during software maintenance activities. These systems contain different categories of issue reports such as bug, request for improvement (RFE), documentation, refactoring, task etc. While logging issue reports into a tracking system, reporters can indicate the category of the reports. Herzig et al. Recently reported that more than 40% of issue reports are given wrong categories in issue tracking systems. Among issue reports that are marked as bugs, more than 30% of them are not bug reports. The misclassification of issue reports can adversely affects developers as they then need to manually identify the categories of various issue reports. To address this problem, in this paper we propose an automated technique that reclassifies an issue report into an appropriate category. Our approach extracts various feature values from a bug report and predicts if a bug report needs to be reclassified and its reclassified category. We have evaluated our approach to reclassify more than 7,000 bug reports from HTTP Client, Jackrabbit, Lucene-Java, Rhino, and Tomcat 5 into 1 out of 13 categories. Our experiments show that we can achieve a weighted precision, recall, and F1 (F-measure) score in the ranges of 0.58-0.71, 0.61-0.72, and 0.57-0.71 respectively. In terms of F1, which is the harmonic mean of precision and recall, our approach can substantially outperform several baselines by 28.88%-416.66%.
format text
author Kochhar, Pavneet Singh
Thung, Ferdian
LO, David
author_facet Kochhar, Pavneet Singh
Thung, Ferdian
LO, David
author_sort Kochhar, Pavneet Singh
title Automatic Fine-Grained Issue Report Reclassification
title_short Automatic Fine-Grained Issue Report Reclassification
title_full Automatic Fine-Grained Issue Report Reclassification
title_fullStr Automatic Fine-Grained Issue Report Reclassification
title_full_unstemmed Automatic Fine-Grained Issue Report Reclassification
title_sort automatic fine-grained issue report reclassification
publisher Institutional Knowledge at Singapore Management University
publishDate 2014
url https://ink.library.smu.edu.sg/sis_research/2439
https://ink.library.smu.edu.sg/context/sis_research/article/3439/viewcontent/iceccs15_reclassification.pdf
_version_ 1770572147250429952