Create an issue template

Create an issue template for bug reports that reviewers can rely on. The template must ask for steps to reproduce, expected versus actual behavior, environment (OS, runtime, version), logs or stack traces attached, and the reporter’s contact for follow-up. Save it under the repository’s issues so every new bug opens with this form enabled.

Before I add the bug issue template, make it easy for triage to prioritize. Put a required severity dropdown at the top, show the exact git commit or version field prominently, and include a short section listing what attachments will make triage faster (repro repo, minimal repro steps, test data). Highlight anything that will make a reviewer hesitate, like “works on my machine” notes or missing logs.

A reporter filed a crash but didn’t include the version or logs. Triage marked it high but can’t reproduce. I’m worried we’ll bounce this extra times and frustrate the reporter. I don’t know if I should ping them for details now or add a stub triage comment and wait 48 hours. What next step gets us a reproducible report fastest without alienating contributors?

We repeatedly spend time asking for environment, logs, and steps before a bug can be fixed. That stalls sprint velocity and burns triage volunteers. Which habit should we change first — stricter issue templates with required fields, an automated bot that requests missing info, or a contributor guide that shows examples? Recommend one change and a practical rollout plan for maintainers.