Bug Triage

General Overview

Open source software projects typically have a bug repository that allows both developers and users to post problems encountered with the software, suggest possible enhancements, and comment upon existing bug reports. Popular open source projects receive lots of bug reports.

Since more bugs are reported than can be easily handled, each bug must be triaged to determine if it describes a meaningful new problem or enhancement, and if it does, it must be assigned to an appropriate developer for further handling.

We are investigating approaches to help automate two parts of the bug triage process:

• Bug Report Assignment
• Duplicate Detection

Our work as been published at a number of venues. See our publications listing below.

• Publications

John Anvik, Lyndon Hiew and Gail Murphy (OK, lousy way to put people on this - other suggestions?)

Bug Report Assignment

One step in bug triaging is assigning a developer to a newly received report. We are developing an approach for semi-automating this assignment. Our approach uses a machine-learning algorithm that is applied to the information about how bugs have been assigned in the past to recommend developers to whom a new bug should be assigned.

In the near future, we will have an assignment tool available that provides a list of recommendations for the following projects:

• Eclipse Platform
• Firefox Browser

The tool will be provided in two formats:

• A Firefox extension.
• An Eclipse plug-in.

E-mail John Anvik if you wish to be informed when the tool becomes available of if you would like to find out if you can use the tool on another project. Note, your project must meet the following conditions to be applicable for our tool:

1. Uses Bugzilla (V.2.16 or higher) for tracking bug reports where the default layout for bug reports has not been altered.
2. The project contains more than 20 developers who actively fix bugs.
3. The project had 1000+ reports marked as FIXED in the last 8 months.

Duplicate Detection

Overview

Publications

• Who Should Fix This Bug?, ICSE 2006.
• Coping with Bug Repositories, eTx Workshop at OOPSLA 2005.