Bug reports
A bug report is a problem raised against a running application, which an agent then investigates. It is the route from "this is wrong" to a fix, without anyone having to work out first which part of the system is at fault.
Raising one
Bug reports come from wherever you are looking at the application:
- from a Test Replay, pinned to the step that went wrong;
- from a UAT session, where your installation has UAT enabled;
- pinned to a specific component of a prototype, HTML or target-stack.
Pinning matters. A report attached to what you were looking at carries the context an investigation would otherwise have to reconstruct — which screen, which component, which scenario, which run.
You can report several pinned problems from one session as one submission, rather than filing them one at a time.
What happens next
An investigation agent picks the report up and works out its scope — whether this is a defect in one feature's implementation, something shared, or a specification problem wearing a bug's clothes. Scope decides who fixes it and where, and getting it wrong is what makes bugs bounce.
The investigation writes up what it found against the report, and you can re-run it. If the first pass missed the point, supply context when you re-run rather than repeating it unchanged — the agent gets what you know, and the second attempt is usually a different answer rather than the same one.
Tracking it
Bug Reports lists what has been raised and where each one got to. A report that results in a code change is tied to that change, so the trail from the pinned screenshot to the commit stays intact.
Where a fix lands depends on the feature's state — see the status table under Implementing a feature. A bug fixed against a feature that has not merged yet lands on that feature's branch; one fixed after it merged goes through the same route any other change does.
Next: Jobs.