Voice workflows

Write reproducible bug reports by voice

Reproduce the bug once, then dictate the environment, the smallest sequence of steps, the expected result, and the actual result. Paste exact errors from logs instead of trying to pronounce them. Review the report as if you had never seen the problem.

By WhisperJot · Documentation reviewed

Record one clean reproduction

  1. Start from a known state, such as a new document or signed-out browser.
  2. Note the app version, operating system, and any setting needed to trigger the bug.
  3. Repeat the smallest sequence that reproduces it. If it is intermittent, record that instead of presenting it as certain.

Speak the observation, then attach exact evidence

A report becomes harder to diagnose when a guess about the cause is written as an observation. 'The save button stays disabled' is observable; 'the database is locked' needs supporting evidence. Keep each in its own part of the draft.

Illustrative example — edit before using
Environment: [app version, operating system].
Steps: Open a new document. Enter a title. Clear the title. Enter a new title.
Expected: Save becomes available again.
Observed: Save remains disabled until I reload.
Frequency: [number of reproductions and attempts].
Evidence: [screenshot or exact error, with sensitive details removed].

Check the report before submitting

For a long report, dictate one section at a time. Keep focus in the same draft while the transcript is being inserted. If text only reaches History, recover it before starting another recording.

  1. Copy exact error messages, stack traces, or identifiers from their source. Do not rely on speech recognition for them.
  2. Read the steps from a clean starting point and fill in missing actions.
  3. Choose a title that names the trigger and symptom. Preview formatting and submit the issue yourself.

Questions

Should I include my theory about the cause?

Yes, if you label it as a hypothesis and separate it from observed behavior. A reliable reproduction and exact error are usually more actionable than a confident guess.

Can dictation capture a stack trace?

Dictation can write your explanation of a stack trace. Copy the actual stack trace from the log so capitalization, punctuation, line numbers, and paths stay exact.

Sources and related guides

Product behavior is based on the documentation below, reviewed 2026-09-09. Examples are authored illustrations; measurement worksheets are for your own observations.

Keep going