Issues related to code quality, including refactoring, improving code structure, and removing technical debt.

Issues related to code or page documentation, including missing or unclear instructions, explanations, or wording changes.

Affects more than 50% of users, prevents optimal/efficient operation of any workflow.

Affects less than 10% of users, or classifies as a "nice to have" feature of a workflow.

Affects ~20% of users, or causes minor alterations to otherwise efficient workflows.

Affects more than 90% of users, or impedes any workflow immensely.

Must be addressed within this (two-week) sprint.

Effectively a backlog item, no set completion timeframe, to be completed at our leisure.

To be tentatively completed in the next 2-3 sprints.

Ultimate priority: must be addressed today, ideally right this very second.

Issues related to critical bugs or oversights which may lead to a possibly security risk, such as account compromise or information leaks.

Issues related to writing or fixing tests, fixtures, factories, ensuring code coverage and stable deployment.

Issues related to software bugs or unexpected behavior that needs to be fixed.

Requests for new features or enhancements to existing features.

Issues related to improving the user experience, such as usability enhancements, accessibility features, or UI/UX improvements.

Issue progress is blocked, usually because it is waiting for administrative decision or feedback. Updated twice daily.

Issues that are currently be worked on. Updated twice daily.

Issues that are ready for potential peer review. Updated twice daily.