TestEngineering/Performance/Triage Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "* When triaging, review new, P1, intermittent, and mentored bugs * Set a priority as early as possible (gut feeling is okay) * Triage search is based on new bugs since last tr...")
 
No edit summary
Line 2: Line 2:
* Set a priority as early as possible (gut feeling is okay)
* Set a priority as early as possible (gut feeling is okay)
* Triage search is based on new bugs since last triage, plus bugs without priority
* Triage search is based on new bugs since last triage, plus bugs without priority
* Always make sure there are enough P1s to work on
* P1: Make sure there are enough to work on
* P1 means someone should be assigned and working on the bug
* P1: Must have someone assigned and actively working on the bug
* If a P1 is blocked, make sure the blocker has an appropriate priority and assignee
* P1: If blocked, link the dependent bugs and prioritise/assign them
* P2 means we can pick up this work when P1 work is blocked or complete
* P2: Must have someone assigned for when it becomes P1 or when P1 work is blocked
* P3 bugs are backlog and are good candidates for community to work on
* P3: Backlog and good candidates for community to work on
* We can plan P3 sprints where we take a break from higher priority work
* P3: We can plan sprints where we take a break from higher priority work
* Consider marking P3 bugs as mentored good first bugs
* P3: Consider marking as mentored good first bugs
* Do not use P4
* P4: Not currently in use
* P5 means we do not intend to fix but will accept a patch
* P5: No intention to fix but will accept patches

Revision as of 10:22, 15 January 2020

  • When triaging, review new, P1, intermittent, and mentored bugs
  • Set a priority as early as possible (gut feeling is okay)
  • Triage search is based on new bugs since last triage, plus bugs without priority
  • P1: Make sure there are enough to work on
  • P1: Must have someone assigned and actively working on the bug
  • P1: If blocked, link the dependent bugs and prioritise/assign them
  • P2: Must have someone assigned for when it becomes P1 or when P1 work is blocked
  • P3: Backlog and good candidates for community to work on
  • P3: We can plan sprints where we take a break from higher priority work
  • P3: Consider marking as mentored good first bugs
  • P4: Not currently in use
  • P5: No intention to fix but will accept patches
Retrieved from "https://wiki.allizom.org/index.php?title=TestEngineering/Performance/Triage_Process&oldid=1222360"