Visual bug reporting

A bug report someone else can reproduce

“Checkout is broken” leaves the next person searching for a starting point. This example names the state, the actions and the result, so a reviewer can try the same sequence.

Written demonstration. The shop and incident below are fictional. This is an example to adapt, not a customer report or a live incident.

Example report

Checkout button stays disabled after correcting the postcode

Preconditions

Use the demonstration shop with one item in the basket. Open checkout as a guest.

Steps to reproduce

  1. Enter an invalid postcode and leave the field.
  2. Replace it with a valid postcode for the selected country.
  3. Complete the remaining required address fields.

Expected result

The postcode error clears and Continue to payment becomes available.

Actual result

The error clears, but Continue to payment stays disabled. Reloading the page and entering a valid postcode first allows checkout to continue.

Reproducibility

Every time using these steps in the demonstration environment.

Environment

Demonstration shop, checkout page. Chrome on macOS, desktop viewport. Add the exact browser version, app release and page address when reporting your own issue.

Impact and workaround

A guest cannot continue checkout after correcting the postcode. Reloading loses the entered address.

Choose evidence that answers a question

For this example, a screenshot would show the completed fields and disabled button. A short recording would show that correcting the postcode does not enable it. Relevant request timing or console errors might help the reviewer investigate, but they do not establish the cause by themselves.

No checkout screenshot or recording is attached to this written example. Capture your own observations and say when evidence is unavailable.

Before sharing

  • Check that the image or clip shows the reported state.
  • Inspect visible text and diagnostics for private details; apply opaque masks where needed.
  • Include only the evidence that helps reproduce or understand the issue.
  • Confirm that the recipient can open the evidence links.

See the review step in tautau

This excerpt shows the real reporting controls with separate demonstration data. It illustrates reviewing diagnostics and sending a report; it is not a recording of the fictional checkout issue above.

Review the evidence before sending12 seconds · silent

Check the captured diagnostics, confirm the review and send.

Actual product footage · demonstration data · edited excerpt

Open full size
Read what happens
  1. The reporter inspects the captured diagnostics.
  2. They confirm that they have reviewed the evidence.
  3. The report is sent to the private team queue.
Explore the feature
Watch the reporting demonstration

Give the next person the same context

A tautau workspace keeps the saved report and its evidence together. A configured Jira ticket includes a private link back to that report. Access to the Jira issue does not grant access to the private tautau workspace.

Real reports remain subject to workspace permissions. This public example contains demonstration text only.