Issue labels

Issue type labels

Name	Meaning	Usage
bug	Acknowledged as bug to be fixed.
enhancement	Describes future enhancements to be discussed and implemented.
a11y	Accessibility Improvement	Accessibility issues should receive a priority label of critical, high, or medium based on severity. The Priority: Low label shouldn't be used for a11y issues.

Name	Meaning	Turnaround Time
Priority: Low	Small impact, resolve as convenient.	Within a month or the next release cycle. These issues should be scheduled but do not require immediate attention, making them suitable for downtime or between larger tasks.
Priority: Medium	Noticeable impact, timely resolution advised.	1 to 2 weeks. These issues are important but not critical, so they should be addressed in a timely manner without disrupting ongoing high-priority work.
Priority: High	Significant impact, prompt resolution required.	48 to 72 hours. High-priority issues affect the user experience or project progress significantly, necessitating prompt action to prevent further issues or dissatisfaction.
Priority: Critical	Major impact, immediate action needed.	Within 24 hours or less. Critical issues often involve major bugs, security vulnerabilities, or anything that could cause significant damage to the user base, project integrity, or company reputation. These issues require immediate attention and should be resolved as quickly as possible, often necessitating an all-hands-on-deck approach.