Bug Wrangling Projects

Here are some ongoing Bugmaster projects to help manage Mozilla bugs. Each one will have bug days or events occasionally, to help its contributors communicate and work together. "Triaging" a bug can mean a lot of different things.

UNCONFIRMED Triage

• Latest Untriaged Firefox bugs, UNCONFIRMED, from the last 60 days.

(Add tips on how to triage these)

Incoming

Bugs Filed Today. All bugs filed in the last 24 hours. Usually this is around 400 bugs, but the number fluctuates over the course of the day.

To work in this area, go through the bugs with status UNCONFIRMED.

• • Today's UNCO Bugs
  • If you can reproduce a bug, and are fairly sure it is a Mozilla bug, mark it NEW.
  • Assign the bug into a product and component, or tag it needs-component
  • Tag the bug with other triage tasks that may be needed.

Websites

This is for bugs that have been reported in Mozilla-run websites.

• Take a look at the Website UNCONFIRMED bugs.
• Sort on Status, ID, or another field.
• Check to see that the bug still exists.
  • If you can't reproduce it, ask the reporter, in a comment with a need-info flag, if they can reproduce it.
    • If they can't, or don't answer after a week or so, resolve the bug as WORKSFORME.
  • If you can reproduce it, mark it NEW and leave a comment to describe what you did. You may be able to find a person to cc on the bug if you look for who has resolved past, similar bugs.

• Websites bugs marked NEW can also use triaging! Here's a bugzilla query for Website NEW bugs reported within the last year.

Accessibility

This is for bug wranglers who would like to help accessibility developers and end users.

• Join #bugmasters and #accessibility

• Meta bug cleanup: this is a very easy task for beginners!
  • Look at accessibility meta bugs
  • Pick one, search for other bugs that are missing, and add them to the meta bug