Bug Triage

Last updated: 2017/09/21

Warning: The bug that will overshadow all the hard work we put into the Firefox 57 release has probably already been filed. We need to find it and fix it.

What we do

Mozilla's bugmaster develops policies and processes for managing bugs, their goal is to "leave no bug behind," and help Mozillians make crisp and actionable decisions on bugs, and enable them to follow-through on their decisions.

Triage Process

If you're triaging bugs in a component, Triage for Component Leads is the process we follow.

Triage Scorecard

Triage status of unresolved bugs in Core, Firefox, Firefox Android, Firefox iOS, and Toolkit (excluding general and untriaged) without open needinfos filed since 2016-06-01

History is viewable as a Re:dash dashboard

Bug Farming

Automated cleanup of bugs is handled by the bug-husbandry-bot, under which regular and ad-hoc queries run.

Current Regular Queries

Intermittent Test Failure Cleanup

Resolves bugs filed from Orange Factor for intermittent test failures. Intermittent test failure bugs which have had no new failures in 21 days (as measured by comment count) and have not been reopened in the past week are resolved as INCOMPLETE.

Inactive Bugs

Resolves bugs in Firefox-related components which have no activity in at least one year. These bugs are resolved as INACTIVE.

Other Requests

File a bug in the Bulk Bug Edit Requests component.

Release Cycle Queries and Activities

1 week to branch

Move fix-optionals

Mark all unfixed, fix-optionals for upcoming release (beta) as wontfix and mark as ? for next release unless that status is set (nightly) (Query)

Update affecteds

Mark all unfixed, affected bugs for upcoming release (beta) as ? for next release unless that status is set (nightly) (Query)

Leave them marked as affected for upcoming release.

Branch day

• Update versions, milestones, tracking, and status
• Add status and tracking for nightly+1 but restrict to release drivers

Stale Bug Reports

• All open bugs without pending needinfos which have had no activity in a year
• All open bugs without pending needinfos with no activity in 2 years
• All open bugs without pending needinfos with no activity in 5 years

• All open bugs with answered needinfos which have had no activity in at least two weeks

• Unconfirmed bugs unchanged in a year

See also, the Chromium Project's automatic triage 'sheriffbot'.

Who we are

• Emma Humphries (:emceeaich), Bugmaster ehumphries@mozilla.com
• The individual triage leads in each bugzilla component

Projects

• Bug Handling: Making sure no bug is left behind
• Bugzilla Clean Up: End-of-life for Bugzilla components
• Bugzilla Folk Knowledge: Documenting how each team uses bugzilla metadata
• Bugzilla Training: Equip Mozillans with best practices on bugs
• Repeat Filers: Track contributions from new Mozillans, so we can get more people filing bugs earlier in the release cycle

Code

• Bugzilla Readable Statuses - enhancement to bugzilla.mozilla.com to help make the status of a bug more understandable
• Triage Center - tool for finding untriaged bugs, and other bugs that need attention
• Triage Report - scoreboard for components with most un-triaged bugs

Meetings

The bugmaster office has no scheduled meetings at this time.

Communication

Get in touch with us. Don't hesitate to communicate using:

• The IRC channel: irc.mozilla.org#bugmasters. Join us on IRC to say hello, introduce yourself, and talk about bugs, bugs, bugs. Questions are welcome!
• Joining the bugmaster mailing list to be informed of all the news and the discussions.

Useful Links

• Triage Leads - who is responsible for triaging new bugs in each Firefox component
• Bugmastering Guide - A guide helping on how to contribute to bug management and triage
• Whiteboard tags - A list of common whiteboard field values and flags used in Bugzilla

Bugzilla Process and Rules

• Bugzilla Etiquette (CoC)
• Guidelines for Restricting Comments
• Comment tagging
• How to request permissions
• Requesting triage permissions