Business analysis glossary
Bug Report
What it is
A bug report describes a defect: something that behaves differently from what was expected. A good one includes steps to reproduce, the expected result, the actual result, the environment and evidence such as a screenshot. Severity says how serious the effect is, and priority says how soon it should be fixed; the two are related but are not the same thing.
Why it matters
Developers cannot fix what they cannot reproduce. Complete bug reports save time for everyone and help the team judge severity fairly. Analysts often help here because they know what the expected behaviour should be, and can check whether it is a real defect or a missing requirement.
Example
"Basket total wrong" is hard to act on. Better: "Using Chrome on the test site, add two items at 20 each and apply code SAVE5. Expected 35, actual 40. Screenshot attached." The improved version tells the developer exactly how to see the problem, so they can find the cause quickly without asking questions.