How Long Will It Take to Fix This Bug?

By Cathrin Weiss, Rahul Premraj, Thomas Zimmermann, Andreas Zeller. IEEE Working Conference on Mining Software Repositories, 2007

410 citations recorded by the source corpus.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/c9f540a5db7668714f193bcec37dc5ce442e9282

How researchers see this paper

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

In Information Systems

In Software

Citations in the corpus

Automated severity assessment of software defect reports (2008, methodology): “In a similar fashion, Lucene (http://lucene.apache.org) a VSM based IR tool, is used in [ 19 ] to predict the time and effort required for fixing a bug.”
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].”
A systematic study of automated program repair: Fixing 55 out of 105 bugs for $8 each (2012, background): “[24] survey 567 effort-tracked issues in jboss (an open-source Java project of comparable scale to our subject programs).”
Modeling bug report quality (2007, methodology): “They use a nearest neighbors technique to predict how expensive a bug report will be to resolve [17].”
History Driven Program Repair (2016, background): “Yet, bug fixing is notoriously a difficult, timeconsuming, and labor-intensive process, dominating developer time [51] and the cost of software maintainance.”
Boa: A language and infrastructure for analyzing ultra-large-scale software repositories (2013, background): “eval? [6]; “What is the average time to resolve a bug reported as critical? [7]”.”
An Empirical Study on Learning Bug-Fixing Patches in the Wild via Neural Machine Translation (2018, background): “w. Eng. Methodol. -, -, Article - (September 2018),28pages.https://doi.org/-.- 1 INTRODUCTION Localizing and fixing bugs is known to be an effort-prone and time-consuming task for software developers [33, 71, 86]. To support programmers in this common activity, researchers have proposed a number of ”
Duplicate bug reports considered harmful … really? (2008, methodology): “Other automated triaging techniques include the assignment of locations to bug reports [6], detection of bug duplicates [10, 17, 19], and prediction of effort for bug reports [21].”
Automated duplicate detection for bug tracking systems (2008, background): “predict the “fixing effort” or person-hours spent addressing a defect [17].”
Improving bug triage with bug tossing graphs (2009, background): “Only few studies have focused on the actual effort that it takes to fix a bug report, mainly because of limited data [29].”