# Browsing bugs on Bugzilla

Estimated time 45 minutes

## Overview

### Questions

• Have you tried browsing the bugs on Bugzilla before?

### Objectives

• If you want to contribute by reviewing or fixing a bug, you need to find bugs that need attention and that you may be able to help with.

## Introduction

This lesson is divided into several challenges that help you with browsing bugs on Bugzilla.

Under construction!

### Challenge 1: Selecting a topic of your interest!

Once your are on the Bugzilla webpage, follow the instructions below to select a topic of your interest:

• Select Browse from the menu
• Look at the topics in R product category
• Select a topic you are interested in/feel comfortable with.

### OUTPUT

[1] "There will be a screenshot of the solution here. Will be added soon!"

### Challenge 2: Filter out a few items!

• Scroll to the bottom and use Change Columns to remove Product and Resolution
• Add Opened and Number of comments

Will be added soon! You can add a line with at least three colons and a solution tag.

### Challenge 3: Order the bug reports!

• Order the bug reports by date
• Keep the most recent at the top

Will be added soon! You can add a line with at least three colons and a solution tag.

### Challenge 4: Categorising the bug!

• Pick a bug with 3-4 comments (one that has received some response)
• Discuss your observations - can you categorise it as one of the following:
• Bug Reporter misunderstands the function/documentation
• Bug can not be reproduced.
• Cause of bug is still being worked out.
• Fix to bug is still being worked out/under debate.
• A solution has been proposed by Bug Reporter or a Bug Reviewer and is waiting approval from R Core.
• An R Core member has committed to implement the fix, but not yet done this.
• Something else - please specify!

Will be added soon! You can add a line with at least three colons and a solution tag.

### Challenge 5: Categorising the bug according to what action needs to be taken next!

• Pick a bug with 1-2 comments (one that has had little response)
• Discuss your observations - can you categorise it as one following, according to what action needs to be taken next?
• Bug is actually a wish list item (suggested new feature) and should be recategorised/discussed.
• Bug needs a (simpler) reproducible example.
• Cause of bug not clear from report and needs investigation.
• There is a proposed fix from the Bug Reporter that needs to be checked and reviewed.
• Needs input on best way to fix from Bug Reviewer or R Core member.
• How to fix is clear, but there is not yet a patch or commitment to fix.
• Bug report has received a negative response (not a bug/not a welcome change) and should be closed.
• Something else - please specify!

Will be added soon! You can add a line with at least three colons and a solution tag.