Write UI bug reports that connect evidence to an expected result

Choose evidence that matches the claim

A useful UI bug report starts with a claim the evidence can support. A screenshot can show overlapping controls or unreadable text. A recording is better when the problem depends on a transition, such as a confirmation dialog opening behind another panel. Choose the medium around the behavior you need to explain rather than adding an attachment only because the issue template has a place for one.

Include the conditions a developer cannot see

Capture the affected interface with safe test data and bring the media into Retick. Note the reviewed build, the user's role, the page location, and any relevant viewport or input conditions in your review context. Those facts may determine whether the problem is reproducible, and the media may not establish them reliably. Avoid including customer information or credentials in the evidence. If private data is essential to diagnosis, follow your organization's approved handling process instead of placing it in public review material.

Example: a confirmation behind a side panel

For a report titled Delete confirmation appears behind the details panel, show the selected record, the delete action, and the obscured dialog. Inspect the proposed finding in Retick to ensure it identifies the actual visual state. Add the shortest reproduction sequence and say whether the confirmation remains reachable. Do not assume the cause is a particular stacking rule unless someone has checked the implementation. A symptom description is sufficient to begin investigation.

Agree on what counts as repaired

Acceptance criteria could require the confirmation to remain visible, its message to be readable, and the cancel and confirm actions to be usable without closing unrelated panels. Confirm these expectations with the product owner. A keyboard interaction concern should receive a separate direct check rather than being declared resolved from the screenshot. Export the reviewed issue to the connected Trello destination and inspect its description before the team accepts it for work.

Keep the evidence current during follow-up

When a fix is available, repeat the scenario on the intended build and compare it against the original report. New screenshots or recordings can document an unresolved state, but a tracker status alone is not visual proof. Retick helps structure the observation and handoff; it does not execute the app across browsers, replace security review, or certify accessibility. Use direct testing and the appropriate engineering tools for claims that go beyond the supplied visual media.