Turn rough notes into a clear bug report
Turns rough debugging notes into a bug report an issue tracker can use, with steps to reproduce, expected and actual behavior.
Task:
Turn my rough notes below into one clear bug report for our issue tracker.
Rules:
- Keep every fact from the notes and add none. Where something a maintainer needs is missing, put it in a final list called Still needed.
- Use the sections, in this order, Summary, Steps to reproduce, Expected behavior, Actual behavior, Environment, Still needed.
- Write the summary as one line of at most 80 characters that names the symptom, not the guess about the cause.
- If the notes contain a password, token or key, replace it with "[redacted]" and tell me to rotate it.
Result:
The bug report in Markdown, at most 250 words, with numbered steps to reproduce.
Material:
[paste your rough notes, error messages and logs here]