Bug reports that know which settings tab you were on

The in-app bug reporter is told the exact settings tab and expanded section you were looking at, so a report reads 'Settings → Team Members' instead of just 'Settings'.

What it is

Settings registers a label for every tab id and pushes the current one into the bug context whenever the tab changes. Individual panels can add finer context — the Access Review panel tags itself only while expanded, because a collapsed section is not a place you are.

Also called: report a problem context · screen context on bug report

See it
Bug reports that know which settings tab you were on
Won
48%
Avg cycle
20d
Pipeline
$395k
JanSep
The bug reporter open over Settings with the breadcrumb reading Settings → Roles & Access. Sample data — no customer information appears here.
How it works
  1. 1registerSubLabels('settings', SETTINGS_TAB_LABELS) declares the label for each hash-derived sub-route.
  2. 2An effect calls setBugContext('settings','tab', label) on every tab change, including the default tab which writes no sub-route.
  3. 3Panels can add data-bug-context attributes conditionally.
Why we built it

Bug reports that name only the top-level view force whoever triages them to guess which of two dozen configuration screens the person meant. Tagging the sub-route makes each report actionable on its own.

The problem
  • Reports filed from Settings carried no indication of which tab was open.
Sound familiar?
What you get
A report identifies the exact configuration screen without the reporter describing it.

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 →