Issue Triage — Vocabulary and Communication Language
Learn vocabulary for triaging GitHub issues: labels, priority, reproducibility, and communication.
0 / 5 completed
1 / 5
What is 'issue triage' in GitHub workflow?
Triage evaluates new issues: verifying they are real, reproducible, and well-described; applying labels (bug/feature/question); assigning priority; and assigning to the right team or milestone.
2 / 5
What does 'needs-reproduction' label mean on a GitHub issue?
'needs-reproduction' signals that the maintainer could not reproduce the issue with the provided information and needs the reporter to provide more context, a minimal reproduction case, or clarification.
3 / 5
What is a 'good first issue' label?
'good first issue' marks well-scoped, approachable issues with sufficient context — designed to help new contributors make their first contribution without needing deep codebase knowledge.
4 / 5
What is 'issue priority' in triage vocabulary?
Issue priority reflects business impact and urgency: Critical (production down, no workaround), High (major feature broken), Medium (significant inconvenience), Low (minor or cosmetic). Drives sprint planning.
5 / 5
What is 'stale issue' management in GitHub?
Stale issue management (often automated with the stale bot) labels issues inactive for e.g. 60 days as 'stale', warns they will be closed in 14 days, and closes them if no response — keeping the backlog manageable.