Intro to Bug Trackers (Activity)

From Foss2Serve
Revision as of 15:04, 16 September 2014 by Heidi.ellis (Talk | contribs)
Jump to: navigation, search


Bug Trackers


Description Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.
Source None.
Prerequisite Knowledge None.
Estimated Time to Completion 60 minutes
Learning Objectives Ability to: 1) Describe the role that a bug tracker plays in a FOSS project, 2) Describe the different types of issues stored in a bug tracker and their priorities, and 3)Identify and track the status of a particular bug in a project.
Materials/Environment Access to Internet/Web and web browser.
Additional Information  ?
Rights Licensed CC BY-SA
Turn In Wiki posting describing the results of your exploration below.


Bug tracking systems are a form of 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, request trackers and ticket systems. Please read the two readings below for a more complete treatment of bug trackers and their use in FOSS projects.


We will begin by looking at a typical Bugzilla instance for a project. We will be using GNOME's Bugzilla instance, but specifically looking at the bugs for the Accessibility Team.

Part 1 - Bug Reports

  1. Open a browser and go to the GNOME Accessibility Bugs
  2. 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.
    1. ID
    2. Sev
    3. Pri
    4. OS
    5. Product
    6. Status
    7. Resolution
    8. Summary
  3. 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)?
  4. Identify the order in which the bugs are initially displayed?
  5. What is the meaning of the shading of some bug reports?
  6. What is the meaning of the colors used when describing a bug (red, gray, black)?
  7. Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
    1. Identify when the bug was submitted.
    2. Identify if there has been recent discussion about the bug?
    3. Is the bug current?
    4. Is the bug assigned? To whom?
    5. Describe what you would need to do to fix the bug.
  8. Repeat the previous step with a different kind of bug.

Part 2 - Collective Reports

  1. Click on the “Reports” link on the top of the page.
  2. How many bug reports were opened in the last week? How many were closed?
  3. What was the general trend last week? Were more bugs opened than closed or vice versa?
  4. Who were the top three bug closers? Why is this important to know?
  5. 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?
  6. Who are the top three contributors of patches?
  7. 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?
  8. Click on the “Generic Reports” link.
  9. Plot the Severity of each Version of the Accessibility features of Empathy.
  10. What other reports can you generate?
Personal tools
Learning Resources
HFOSS Projects