Session Replay: severity, steps to reproduce and a likely cause, written from the capture
A report nobody had to write. The recording sits on the left and everything collected with it on the right, and the Analysis tab suggests how serious it is, sets out how to reproduce it with the source of every step, and offers a likely cause.
Расшифровка
Let us look at a report that came in this morning, and at what the product had already made of it before anybody opened it.
On the left is the recording of what the customer actually did. On the right, everything that was collected while it happened.
Even the heading was written from that capture. Nobody sat down and titled this.
The analysis tab is where it does the triage a person would otherwise have to do.
It suggests how serious this is, and says what that judgement rests on.
It sets out how to reproduce it, and every step points back at the thing it was read from: a page, a click, a request that failed.
And it offers a likely cause, which is usually the part that saves the afternoon.
The other tabs hold the evidence underneath it. The timeline, the console, the network.
All of it read from a recording, and none of it from the person who hit the bug.