Improving bug triage with bug tossing graphs

479 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.

What distinguishes great software engineers? (2019, background): “Bug triaging, examined by many researchers (Anvik and Murphy 2007; Jeong et al. 2009; Podgurski et al. 2003; Runeson et al. 2007; Bertram et al. 2010) is effectively a decision-making process.”
Transfer defect learning (2013, background): “Transfer learning may benefit other prediction and recommendation systems [57], [58].”
Work Practices and Challenges in Pull-Based Development: The Contributor's Perspective (2014, background): “[19] or [20]) is not directly applicable to the pull-based model, as a pull request is not necessarily as static as a bug report.”
Predicting the severity of a reported bug (2010, methodology): “Text mining techniques have been previously applied on these descriptions of bug reports to automate the bug triaging process [1, 2, 3] and to detect duplicate bug reports [4, 5].”
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”