A2UI Issue Triage Criteria & Guidelines
This document defines the operational execution rules for classifying issues, assigning priorities, recommending owners, and drafting responses.
Canonical Sources of Truth
Refer directly to the project documentation for authoritative definitions and canonical response templates:
- Priority Definitions & Invariants: docs/contributing/triage/triage.md (
P0throughP3). - GitHub Status Labels: docs/contributing/triage/labels.md (
status: first-line-handled,status: waiting-for-author-response,status: needs-team-input,status: needs-triage). - Canonical Response Templates: docs/contributing/triage/templates.md (Standard replies for requesting information, compliance reports, assigned issues without priority, stale issue pings, and out-of-scope requests).
Issue Classification & Operational Action Flows
All triaged issues must be tagged with the status: first-line-handled label.
1. Bug Reports
- Analysis:
- Reproduction: Do not attempt local reproduction unless the steps are simple, clear, and the environment can be set up immediately. If you need to check out the branch or clone the PR repo to reproduce the issue, do it in a temporary clone or git worktree (e.g. in
<appDataDir>/brain/<conversation-id>/scratch/issue_12345_repro/). - Static Analysis: For complex bugs, analyze the logs, stack traces, and relevant specification files (e.g., JSON schemas in
specification/) to diagnose the issue.
- Reproduction: Do not attempt local reproduction unless the steps are simple, clear, and the environment can be set up immediately. If you need to check out the branch or clone the PR repo to reproduce the issue, do it in a temporary clone or git worktree (e.g. in
- Action:
- If reproduction steps or logs are missing, set action to
needs_info, apply thestatus: waiting-for-author-responselabel, and use the Requesting information template. - If verified, suggest the appropriate priority (
P0toP3) and recommend the owner of the affected component based on path mapping (e.g., paths withtypescript/renderers/litbelong to the Lit renderer maintainer,specification/to the specification maintainer) and file commit history (git log -n 5 --format="%ae" <file>). - Clean up any temporary files, worktrees, or clones when finished.
- If reproduction steps or logs are missing, set action to
2. Feature Requests
- Analysis:
- Verify if the request aligns with the A2UI roadmap and design philosophy for the affected components.
- Action:
- If aligned, set action to
backlogwith priorityP2orP3and suggest component/type labels (e.g.,component: standard catalog specification,type: feature/enhancement). - If out of scope, set priority to
Noneand action toclose_invalid(closes the issue as not planned). Draft the response using the Out of Scope template.
- If aligned, set action to
3. Support Requests and Questions
- Analysis:
- Identify if the issue is a question about usage or setup rather than a bug.
- Action:
- Set action to
close_resolvedorclose_invalid. - Answer the question directly or provide links to relevant guides (e.g., quickstart.mdx) or GitHub Discussions, then close the issue.
- Set action to
Response Guidelines
When drafting replies, always copy the exact response text from docs/contributing/triage/templates.md.
- Be direct: State the action being taken or what is needed immediately.
- Eliminate fluff: Do not use conversational filler (e.g., "I hope this helps").
- Refer to templates: Keep draft comments synchronized with canonical templates.