Report an Issue

Create a clear, actionable issue in the right tracking system. Your job is to capture and structure the problem — not to solve it. A well-written issue enables someone else to understand, reproduce, and fix the problem without asking follow-up questions.

Process

1. Gather information

Read the context carefully before asking anything. Often the user has already described the problem — extract what you can from the conversation.

If you're called from triage-bug, the root cause analysis and TDD plan are already in context — include them in the issue body.

Only ask for missing details if they're essential for someone else to understand or reproduce the problem. Prefer one focused question over multiple sequential ones.

Key information to collect:

• What happened (actual behavior)
• What should have happened (expected behavior)
• How to reproduce (steps, if applicable)
• Environment (OS, version, runtime — only if relevant)