P0Critical, release-blocking impact on users or business. Requires immediate, hands-on attention.checkout is down for all users
Issue triage
Priorities
A shared scale for how quickly an issue should be tackled. Every issue is tagged with a priority so the team can agree on what gets picked up first.
Priority levels
P1High impact on users or business, but less urgent than P0. Schedule for the current sprint when possible.session refresh breaks token renewal
P2Important work that affects users or operations, but is not time-critical. Address within the next few sprints.slow explorer sidebar on large trees
P3Noticeable but limited impact. Schedule for future sprints once higher-priority work is done.polish empty-state copy
P4Low priority with minimal impact. Handle as time permits or keep on the backlog for later.document edge-case behaviour
How to choose
Fix the most blocking work first
Work that blocks a release or affects many users takes priority over work that can wait. A P0 should be picked up before a P2, even if the P2 looks more interesting.
Tie priority to user impact
Estimate how many people are affected and how badly. The more users affected and the more it breaks the workflow, the higher the priority.
Re-evaluate as things change
Priorities are not permanent. Revisit a card when a workaround appears, a customer is blocked, or a release deadline moves, and promote or demote it accordingly.