What does it mean for a bug report to contain "one bug per report"?

A bug report containing "one bug per report" emphasizes clarity and focus in communication about defects found in software. By isolating each bug in its own report, the development team can more easily understand, prioritize, and address the issues without the confusion that may arise from combing multiple bugs into a single report.

This approach aids in tracking the status of each bug individually, facilitating clearer discussions during triage sessions and ensuring that specific fixes are targeted without ambiguity. It helps to eliminate the possibility of a situation where resolving one issue inadvertently leads to the neglect of another, which might be hidden among multiple reports. Additionally, it allows for precise documentation of symptoms, steps to reproduce, and expected vs. actual results for each bug, making it easier for all stakeholders to ensure that specific issues are resolved effectively.