Create browser recording bug reports with a reproducible story

Record the smallest meaningful failure

A browser recording is most useful when it answers what happened before the broken state appeared. Start from a recognizable page, perform the necessary actions, and pause on the result. Avoid a long exploratory session with unrelated tabs and repeated attempts. If the failure requires a particular role, viewport, or test record, write that context down rather than assuming the viewer will infer it from the video.

Make capture safe and understandable

Use the Retick browser extension to capture the relevant workflow, then review the media before sharing it. Work with test accounts and safe data, and keep credentials, personal messages, and unrelated browser content out of view. Explain the intended behavior briefly if it is not obvious. A useful example is selecting an item, opening its details, returning to the list, and finding the previous selection unexpectedly cleared.

Turn the sequence into a report

After processing in Retick, inspect the proposed findings against the recording. Confirm the order of actions and whether a deliberate reset or changed filter could explain the result. For an issue titled List selection disappears after returning from item details, add the starting selection, navigation path, and observed state. Distinguish a confirmed failure from an intermittent symptom that still needs reproduction. Remove any generated explanation that asserts a cache or server fault without supporting technical evidence.

Define the check that would accept a fix

Agree on whether the product should preserve selection when a user returns to the list. Acceptance criteria might require the same item to remain selected and the available bulk actions to reflect it. Also check the empty selection case so the fix does not retain an item when a user has explicitly cleared it. Export the reviewed report to the connected Trello destination, and inspect the resulting description before assigning it through the team's normal process.

Keep recording evidence separate from execution evidence

The captured session documents behavior in one environment. It does not establish that the bug occurs in every browser, identify the underlying implementation cause, or prove that an attempted repair is correct. Reproduce important cases directly and use dedicated developer tools for logs, network inspection, and automated tests. After a fix, make a fresh manual pass through the same sequence and record any remaining discrepancy instead of closing the concern solely because the tracker says it is done.