Reducing the effort of bug report triage: Recommenders for development-oriented decisions

326 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Deep Code Search (2018, methodology): “Besides code search, there have been many other information retrieval tasks in software engineering [8, 9, 16, 23, 24, 29, 51, 55, 63, 67] such as bug localization [66, 73, 80], feature localization [19], traceability links recovery [20] and community Question Answering [11].”
What Makes a Good Bug Report? (2008, background): “Several studies used bug reports to automatically assign developers to bug reports [4], [5], [20], assign locations to bug reports [19], track features over time [26], recognize bug duplicates [22], [29], [32], [54], [60], assess the severity [44], predict effort for bug reports [63], identify bug t”
It's not a bug, it's a feature: How misclassification impacts bug prediction (2013, methodology): “But bug fixes have also been used to estimate development efforts [19], [20], [21], [22], bug triage [23], [24] or automatic bug assignment [25], [26].”