Practice the vocabulary of reviewing and categorizing newly filed issues before they enter the backlog.
0 / 5 completed
1 / 5
At standup, a dev mentions a queue where newly filed issues wait to be reviewed, categorized, and either accepted or declined before entering the active backlog. What is this workflow stage called?
A triage queue holds newly filed issues in a distinct stage where they're reviewed, categorized, and either accepted into the active backlog or declined, rather than flowing directly into the sprint board unreviewed. This gatekeeping step prevents low-quality, duplicate, or out-of-scope issues from cluttering the team's active work. It's a common practice for teams receiving issues from multiple sources, including external bug reports.
2 / 5
During a design review, the team wants every new issue to automatically get a priority label based on keywords in its title and description. Which capability supports this?
Automated triage rules apply a priority label, or other categorization, to a new issue automatically based on patterns like specific keywords in its title or description, reducing the manual effort of triaging every incoming issue individually. This speeds up the triage process for a team receiving a high volume of issues. It requires carefully designed rules to avoid consistently mislabeling issues that don't match the expected keyword patterns.
3 / 5
In a code review, a dev notices a triaged issue was automatically linked to a related, previously reported issue with similar wording. What does this represent?
Automated duplicate or related-issue detection identifies a newly filed issue's similarity to an existing one, letting the team merge duplicates or connect related reports without someone having to manually search the backlog for a match. This reduces redundant work being tracked and discussed separately under multiple issues. It's especially valuable for a team receiving many external bug reports that describe the same underlying problem in different words.
4 / 5
An incident report shows a critical bug sat untriaged for a week because no clear ownership existed for reviewing the triage queue. What practice would prevent this?
Assigning clear, often rotating ownership for reviewing the triage queue ensures someone is regularly checking it, rather than leaving it to chance that a critical issue gets noticed. Leaving the queue effectively unowned is how a genuinely urgent bug can sit unreviewed for an extended period. This ownership structure is a standard practice for any team relying on a triage stage to catch and prioritize incoming issues promptly.
5 / 5
During a PR review, a teammate asks why the team maintains a separate triage stage instead of letting every new issue go straight into the active sprint backlog. What is the reasoning?
Letting every new issue go straight into the active backlog means low-quality, duplicate, or out-of-scope issues consume the same visibility as genuinely important, well-scoped work. A triage stage filters and prioritizes issues before they reach that active backlog, keeping it more focused. The tradeoff is the ongoing effort required to actually review and process the triage queue regularly.