UXE REPLAY

Every bug has a backstory.

UXE Replay turns a tester's one-tap report into an evidence bundle: what happened, where, and what led up to it.

One-tap report flow

1Tester hits an issueSomething looks wrong.
2One-tap captureScreenshot plus context.
3Evidence bundleConsole, network, DOM, events.
4Routed to the teamGlitchTip and Jira (internal).
5Verify or rejectClose the loop.

Evidence bundle

Screenshot

What the tester saw.

Available (internal)

Console and network

Logs and HAR.

Available (internal)

DOM snapshot

Page state at report time.

Available (internal)

UXE events

Semantic event sequence behind the Backstory.

Available (internal)

Backstory

Checkout button not respondingUAT session · 1d ago

Open

Console logs24 entries

Network18 requests

DOM snapshotat report time

User journey9 steps

Event replaywhere supported

Attachments3 files

Illustrative example — mock data, not a real report.

Session event stream

00:12screen_viewProductDetail
00:15tapsize_selector
00:18tapadd_to_cart
00:21errorPOST /cart → 500
00:22tapadd_to_cart (retry)
00:24report_filedUXE Replay

Illustrative example — mock data, not a real report.

Related sessionReplayConsoleNetwork

00:12Page viewed
00:18Clicked “Add to cart”
00:21Error: request failed
00:22User tried again
00:24Report filed

Illustrative example — mock data.

Reports land in GlitchTip tagged with the UAT session, and flow to Jira in our internal environment. A reviewer verifies or rejects the fix. Available on web via the SDK and as an iOS/macOS app.

UXE Replay is private and internal-first, and designed for non-production environments. These integrations are not generally available.

Help shape what comes next.

UX Events and UXE Replay are in private early access.

Request Early Access