bug-reportlisted

# Report a bug A bug report has one job: get the defect fixed with the fewest round trips. Every round trip costs a day. Most of what makes a report bad is the reporter knowing something and not writing it down. ## Steps **1. Reproduce it.** From a clean state, following your own steps. If you cannot, say so in the report and say how many times you tried. An intermittent bug is still worth filing, but it has to be labelled as one or someone will close it as not reproducible. **2. Narrow it.** Cut every step that is not needed. Ten steps become four. Then ask which is the real variable: does it happen with a different account, a different browser, a different amount? The answer usually points at the cause and saves the developer the search. **3. Check it is new.** Search the tracker before filing. A duplicate splits the discussion across two tickets. **4. Work out what it costs.** Not how annoying it is. How many users, how often, what happens if it ships, and whether there is a workaround. That is what someone prioritises on. **5. Write it.** Shape below. **6. File it.** Per `tracker` in `qa.config.yml`: - `jira`: create the issue with the Atlassian tools, in `tracker.project_key`. - `github-issues`: `gh issue create`. - `none`: write it to a file and tell the user where. Attach what you have: screenshot, trace, video, the failing test output, the network log if the failure is a request. ## Shape ```markdown # <One line. What is wrong, where. Not "checkout broken"