Background

Bug tracking systems are a tool for change management and organization used by FOSS projects.
Bug trackers do far more than simply keep track of bugs.
They also are used to hold new feature requests, patches, and some tasks.
Bug trackers are also called request trackers, issue trackers, and ticket systems.
Please read the two readings below for a more complete treatment of bug trackers and their use in FOSS projects.

Part 1 - Bug Reports

Define what each of the column names below indicate. Include the range of possible values for 2-7 below. Feel free to explore beyond the page to find more information.

ID

Sev

Pri

OS

Product

Status

Resolution

Summary

Describe how you discovered the definitions and how did you find the information from above (hint: the advanced search shows the options or the Reports link has a link).

Identify the order in which the bugs are initially displayed.

What is the meaning of the colors used when describing a bug (red, gray, black)? (Hint: click on the Bug ID and examine the fields)

Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).

Identify when the bug was submitted.

Identify if there has been recent discussion about the bug?

Is the bug current?

Is the bug assigned? To whom?

Describe what you would need to do to fix the bug.

Repeat the previous step with a different kind of bug.

Part 2 - Collective Reports

Click on the “Reports” link on the top of the page.

Click on the "Summary of Bug Activity for the last week".

How many bug reports were opened in the last week? How many were closed? (254 reports opened and 220 reports closed

What was the general trend last week? Were more bugs opened than closed or vice versa? There were more bugs opened than closed

Who were the top three bug closers? Why is this important to know? Nick Wellnhofer: 37, Matthias Clasen: 14 and Michael Schumacher: 9. It is important to know who are the best contributors to fixing and closing bugs in the system to ask them for help when needed

Who were the top three bug reporters? Are these the same as the top three bug closes? What is the overlap in these two lists? Piotr Drąg: 9, Stephen: 8 and Mohammed Sadiq: 7. They are not the same as the top three bug closes. Bug reporters are the ones who report finding bugs when tey try the system and they are not necessarily the same people who can fix those bugs and close them

Who are the top three contributors of patches? Debarshi Ray: 24, Florian Müllner: 22 and Georges Basile Stavracas Neto: 9

Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers? Florian Müllner, Debarshi Ray and Sebastian Dröge (slomo). Two of the top contributers of patches are among the top patch reviewers but non of the top three contributors of patches or reviewers of patches were involved in closing the bugs

Click on the “Generate Graphical Reports” link.

Plot a line graph of the severity of bugs by component for Orca:

Select "Severity" for the vertical axis

Select "Component" for the horizontal axis

Select "Bar Graph" for type of graph

Leave the "Multiple Images" as <none>

Scroll down and select Orca from the Product menu.

Click "Generate Report".

What class were the majority of the bugs for braille? Normal and General components