2019
DOI: 10.1016/j.infsof.2019.07.009
|View full text |Cite
|
Sign up to set email alerts
|

Bug report severity level prediction in open source software: A survey and research opportunities

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
39
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 42 publications
(39 citation statements)
references
References 29 publications
0
39
0
Order By: Relevance
“…From the literature review perspective, Gomes et al [2] conducted a mapping study on automatic bug prioritization. The authors reported ten different aspects of the experiments from the selected studies.…”
Section: A Prioritization Of Bug Reportmentioning
confidence: 99%
See 2 more Smart Citations
“…From the literature review perspective, Gomes et al [2] conducted a mapping study on automatic bug prioritization. The authors reported ten different aspects of the experiments from the selected studies.…”
Section: A Prioritization Of Bug Reportmentioning
confidence: 99%
“…In the bug repository, any developer, end-user, or tester can report the bug by filling a form of the specific repository. According to the published reports [2], [3], Eclipse [4] had 250,000 bug reports in 2009, while 84,245 bug reports have been submitted from 2013 to 2015 indication an average raise of 120 new bug reports on daily basis.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Staked denoising auto-encoder (SDA) is a method of feature learning that is used for DR.They have reported that BPDET has out-performed on most of the datasets and BPDET is tested using Wilcoxon rank-sum test and as a result, null hypothesis is rejected at α = 0.025. Gomes et al [43] performed a comprehensive mapping study in which he had reviewed recent research efforts on automatically bug report severity prediction and for this he had selected 54 papers. They reported that 27 studies are addressing bug report severity prediction on Free or Libre Open Source Software.…”
Section: Related Workmentioning
confidence: 99%
“…Based on this information, one or more analysts, namely triagers, decide processing priorities and assign bug reports to software developers for correction. As shown in past studies [1][2][3][4][5][6], the severity attribute of a bug report is an important factor that influences its processing priority in the schedule of bug fixing activities that follow. When a bug report is submitted to a bug tracking system (BTS), such as Bugzilla (https: //www.bugzilla.org, accessed on 7 July 2021) or MantisBT (https://www.mantisbt.org, accessed on 7 July 2021), the reporter generally assigns a severity level to the bug report based on personal judgement.…”
Section: Introductionmentioning
confidence: 96%