Turn rough notes into a reproducible bug report

A bug report should separate observed behavior from the reporter’s theory. Include enough environment and input detail for someone else to attempt reproduction.

Use a reviewable project copy

Give the product or code teammate the relevant specification and a dedicated project folder or branch. Separate a proposed change from permission to release it. Request a diff or evidence table alongside the recommendation, and run checks that exercise the behavior in question. Generated code and test output still need review in the actual project environment.

Inputs for this workflow: Sanitized notes, application version and permitted sample input.

Work through the task

1. Extract exact steps and observations.
2. List missing reproduction information.

A brief you can adapt

Draft bug-report.md with environment, steps, expected result, actual result and evidence. Put suspected causes in a separate hypothesis section.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Have another person follow the steps using the sample and record whether the same behavior occurs.

Where this approach can fail

Do not claim a root cause or successful reproduction that was not actually checked.

For the related desktop setup, see local folder.