DOM/Triage

Overview

Bugmasters/Process/Triage#How_Do_You_Triage gives an overview of how we do triage and what each priority means.

New bugs - do this daily

Let's ensure newly-filed bugs in a variety of DOM-ish components are actionable as soon as possible after their filing. This doesn't mean we're going to fix them sooner but that they'll be fixable when we get around to attempting to fix them. Inspiration taken from Platform/GFX/TriageSchedule.

• is this bug in the correct component?
• do we need a regression range?
• needinfo for more information, e.g. URL, STR, or module owners' comment, if you can't decide the priority right at the moment
• note: an assumption here is that bugs with non-nobody assignees are progressing towards a fix in some way

New "DOM" bugs that need actions

Unanswered-needinfo new bugs - do this daily if possible

• is there an outstanding needinfo request for any missing information?
  • is there someone else who could answer?
  • is there a more appropriate person to needinfo?
  • see above for other tips for dealing with new bugs
• do these people or their managers need to be emailed?
• Set priority if you've done above and there's no pending needinfo so it doesn't show up in tomorrow's list

Unprioritized "DOM" bugs with outstanding needinfo?

Orange bugs - do this daily if possible

• are any of these in areas you can fix?
• are any of these in DOM-ish components that aren't getting traction? can you politely nudge someone on the team to take a look?
• are any of these obviously in the wrong component and moving them would help get closer to a resolution?

Top orange bugs

P1 bugs - do this weekly

• is there is an assignee?
• is there anything needed to make this bug move forward?

DOM P1 bugs

Chipping away at bugs that may have been forgotten - doesn't have to be done daily

• is there anything needed to make this bug actionable?
• is this bug being prioritized appropriately?
• is this bug even valid anymore?

"DOM" old bugs that need re-prioritization or re-validation

Moving btpp-* bugs into corresponding priority buckets

The mapping b/w btpp-* and priorities we are currently using:

• btpp-fixnow => P1
• btpp-fixlater => P2
• btpp-active => P1 or P2
• btpp-backlog => P3 or P5

We basically should treat btpp-followup bugs as New bugs or Unanswered needinfo bugs.

DOM bugs with whiteboard btpp-{fixnow,active,fixlater,backlog}

DOM bugs with whiteboard btpp-followup

Priority nomination

Make P2s to P1s, and P3s to P2s/P1s after review. Nomination happens at least once a release.

DOM P2 bugs

• are any of these super-urgent and thus really P1?
• if we marked something as P2 and it's been that way for a while, do we really need to keep it as such or could it become a P3?

DOM P3 bugs

Bugzilla Query List

DOM P1 bugs

DOM P2 bugs

DOM P3 bugs