The report knows where you were

Every report, feature request and task filed from the app records the module, the sub-tab, the open dialog and the exact record you were looking at — without you typing any of it.

What it is

A three-layer capture runs at the moment you open the dialog. It reads the sub-route from the hash, scans the DOM for the topmost visible dialog and reads its heading, and picks up explicitly registered state like which contact is selected or which stage a card sits in. All three feed one envelope with a canonical module id shared across bugs, feature requests and tasks.

Also called: automatic context · screen capture context · what page was I on · reproduction details

See it
The report knows where you were
Won
39%
Avg cycle
19d
Pipeline
$610k
JanSep
The report form showing an auto-filled context strip — module, sub-tab, open dialog title, selected record — that the user never typed. BugReporter.tsx reading contextEnvelope.captureEnvelope(). Sample data — no customer information appears here.
How it works
  1. 1Layer 1: the router keeps the open tab in the hash, so 'Settings → Team Members' is derivable with zero instrumentation
  2. 2Layer 2: a DOM scan finds the topmost visible dialog and reads its heading — this works across 100+ modals without tagging any of them
  3. 3Layer 3: explicit context entries for state the DOM cannot express, scoped to the owning view so a hidden view's stale selection is never reported
  4. 4The envelope resolves a canonical module id from the same enum the architecture map is drawn from
Why we built it

A report saying 'the totals are wrong on this screen' is worthless when nobody can tell which screen, which job, or which of the numbers. Worse, the same screen used to be labelled three different ways depending on whether you raised a problem, a request or a task from it, so nothing could be counted or compared — one button produced three different names for one place. Every report now carries the area of the app, the sub-tab, the dialog that was open and the exact record you were looking at, under one shared vocabulary, and none of it is typed by the person filing. It also refuses stale context: a customer you had open hours ago cannot attach itself to a problem you hit somewhere else this afternoon.

The problem
  • Reports lack the exact screen, tab, dialog and record needed to reproduce
  • The same screen is named differently by every intake path, so nothing can be counted
Sound familiar?
What you get
Zero extra typing for the reporter
Bugs, ideas and tasks can be grouped and counted by module
New modals get context capture for free the day they ship

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →