Bug Priorities

P0 (Critical/Urgent/High Priority)

• Definition: Catastrophic issue affecting most or all users in production, resulting in primary workflow disruption.
• Examples: System crash, data corruption, major security vulnerability, login failures, core functionality inaccessible. Primary workflow in production is unusable.
• Resolution: Follow the Incident Response Plan

P1 (Medium-High Priority)

• Definition: Functionality impeded for a specific subset of users, or a bug blocking secondary workflows.
• Examples: Issues in specific user roles, errors in optional features, or sporadic performance issues.
• Resolution: Write up a Production bug ticket. A sub-team engineers a fix, and we release a hot fix. On staging these block the next release.

P2 (Medium Priority)

• Definition: Defects causing inconvenience but not preventing users from completing core tasks.
• Examples: Minor functionality issues, cosmetic bugs in critical workflows, prominent spelling errors (e.g. proper nouns) or rare errors with easy workarounds.
• Resolution: In production these issues are prioritized for the next release if discovered mid-sprint. On staging
• these block the next release.

P3 (Low Priority)

• Definition: Low-impact bugs affecting non-critical areas or niche scenarios that do not affect core functionality.
• Examples: Display issues in low-traffic areas, mild inconsistencies in UI behavior, buried spelling errors.
• Resolution: In staging or prod these issues are ticketed and considered for the next sprint. We don’t block the release for these issues.