A bug report can be a reusable record

The best bug reports become small API-readable records: environment, trigger, observed result, expected result, and fix status.

A good bug report is not only for the developer who fixes it today. If it keeps environment, trigger, observed result, expected result, and fix status in a stable shape, it becomes useful later for search, release notes, support pages, and lightweight assistants. The prose can be short; the record shape matters more.