2020
DOI: 10.1016/j.asoc.2020.106667
|View full text |Cite
|
Sign up to set email alerts
|

Learning to rank developers for bug report assignment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2022
2022
2025
2025

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 25 publications
(7 citation statements)
references
References 13 publications
0
7
0
Order By: Relevance
“…Similarly, Alkhazi et al. [21] extract information from commit messages and treat it as domain knowledge to create developer profiling features, which are thereafter used to determine the most suitable developers for resolving a bug report. An interesting alternative is proposed by Sajedi‐Badashian and Stroulia [22].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Similarly, Alkhazi et al. [21] extract information from commit messages and treat it as domain knowledge to create developer profiling features, which are thereafter used to determine the most suitable developers for resolving a bug report. An interesting alternative is proposed by Sajedi‐Badashian and Stroulia [22].…”
Section: Related Workmentioning
confidence: 99%
“…To do so, they use a dataset extracted from GitHub [20] and employ a neural network that aggregates features probabilities in order to automate the assignment of GitHub issues. Similarly, Alkhazi et al [21] extract information from commit messages and treat it as domain knowledge to create developer profiling features, which are thereafter used to determine the most suitable developers for resolving a bug report. An interesting alternative is proposed by Sajedi-Badashian and Stroulia [22].…”
Section: Related Workmentioning
confidence: 99%
“…Several studies on software engineering have demonstrated that the deadline pressure and the developer's inexperience are among the factors that may lead to the introduction of the so-called technical debt [1,2], which refers to a group of design issues that may affect the software's maintenance as well as its evolution in the future [3,4]. Code smells (a.k.a.…”
Section: Introductionmentioning
confidence: 99%
“…Motivated by this observation, researchers have paid attention to code smell detection [10] and they have proposed different techniques to automatically detect code smells within software systems codebases [4]. These techniques could be classified into three categories: (1) rule/heuristic-based approaches [11], (2) machine learning-based approaches [12], and (3) search-based ones [13]. Mantyla et al have been discussing the uncertainty issue as one of the major individual human factors that may influence software engineers' decisions about the smelliness of software classes for more than fifteen years, and more specifically since 2004.…”
Section: Introductionmentioning
confidence: 99%
“…Many studies classify app reviews using different taxonomies [91,105,148,203,241,245,24,26,37,25,173], for various purposes: detection of potential feature requests, bug reports, complaints, and praises, etc. Even though many of them identify reviews related to app usability, there is no explicit mention of accessibility-related issues [112].…”
Section: Classification Of Text Documentsmentioning
confidence: 99%