Bug reports that write themselves.
Your team dogfoods and captures issues before users hit them.
- For
- The team itself, testing its own product before a release.
- Leads with
- Record with screen
- Preset goals
- 4 — editable, up to five
- Also uses
- The Chrome extension — record the tab you are already in
Your team captures as it tests, so the ways in are fast and in the moment — before the detail is lost.
The gap between finding a bug and writing it up is where bugs go to die. Nobody wants to stop mid-session, switch to the tracker, and reconstruct what they just did. So capture is one click from the tab you are already in, and the write-up happens after.
The capture routes this project puts in front of you.
All seven capture methods work in every Sense project. This template only decides the order — and for internal testing, that order starts here.
Capture your screen and your voice together, so what you say lands next to what you did.
Paste a meeting link and the Sense Bot joins the Zoom, Meet, or Teams call, records it, and transcribes it.
Record a voice note in the browser — the fastest way to get a thought down right after a session.
Drop in audio, video, or a document you already have and we will transcribe it.
4 preset goals, written for this situation.
A goal is an extraction prompt: it tells the AI what to pull out of every transcript in this project. These ship with the template and are yours to rewrite — a project holds up to five.
Expected vs. actual behavior, steps to reproduce, the affected screen, and severity — crash, data loss, or no workaround, against merely minor.
What previously worked and now does not: what changed, when it last worked, and the specific flow affected.
Rough edges that are not strictly broken — confusing labels, awkward flows, inconsistent UI, and the friction your own team hits.
Unusual inputs, permissions, empty or large states, boundary conditions, and incorrect or missing data.
One line becomes an action item, without losing the words.
Nothing here is a summary. Each hop keeps a link back to the one before it, so the item at the bottom still opens onto the sentence at the top.
- 01Capture
Someone hits record on the tab they are already in, screen and voice together. Two testers on one screen-share session.
app.example.comREC1:08Finish - 02Signal
It lands as a transcript — timestamped, searchable, with the recording attached.
0:02PriyaFiltering to open items, then opening one to check the detail view.0:09PriyaWait — the filter reset itself when I hit back. That definitely worked last week.0:15TomSame on mine. Sort order goes too, not just the filter. - 03Anchor
Read against this project's 4 goals, the passage that answers one gets lifted out verbatim and tagged. The anchor keeps its offsets into the transcript.
0:02PriyaFiltering to open items, then opening one to check the detail view.0:09PriyaWait — the filter reset itself when I hit back. That definitely worked last week.0:15TomSame on mine. Sort order goes too, not just the filter.Tagged toRegressions - 04Insight
Anchors group into a finding. One insight often draws on more than one goal.
Going back from a detail view drops both the filter and the sort order
3 anchorsRegressionsUsability & polish - 05Action item
The finding becomes a backlog item on the workspace kanban, still linked to the anchor it came from.
Preserve filter and sort state on back navigationTodoTraces back to Priya at 0:09
Every capture becomes a signal, and the insights land in your backlog as action items.
Action items live on the workspace backlog, not inside a single project — so a fix that came out of a testing session sits next to one that came out of an interview, each carrying its own evidence.
The session is the ticket.
- Nobody writes repro steps. The repro is in the recording, and the anchor is the moment it broke — timestamped, with the screen next to the words.
- "That definitely worked last week" is what makes it a regression rather than a bug. The goals are written to tell those apart instead of dumping both in one pile.
- The Chrome extension records the tab you already have open, so finding the bug and filing it are the same action.
Record the tab you just found it in
The extension carries the capture for this template. Hit record on the tab you are already in, keep testing, and the session arrives in this project as a signal — so finding the bug and filing it are the same action.
- One click from the tab, so finding it and filing it are the same action
- Screen and voice on the same clock — what you say lands next to what you did
- Picks the project before you record, so the capture arrives already filed
The Chrome extension and the feedback widget solve the same problem for different audiences. This template ships with the extension; collecting user feedback ships with the widget.
All seven capture methods are available in every project. A template only decides what you see first.
Rewrite, remove, or add to the preset goals at any time. A project holds up to five.
A new workspace is seeded with one project per template. Nothing is locked behind a choice you make on day one.
Every anchor carries its citation offsets into the transcript, so each claim traces back to the words that were said.
Every workspace starts with this project already in it.
Create a workspace and all six projects are seeded for you — this one included, goals and capture order set up. Nothing to configure before your first capture.
Your first run in this project ends on “Start recording”. The project tour spotlights the recorder, so the first run ends with a real capture.