TestEngineering/Performance/Triage Process

• 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