Back to blog

How to Dictate a Bug Report Someone Can Reproduce

Use voice for the sequence you observed, add exact technical details by hand, and check the ticket from the next person’s point of view.

Nov 9, 2026Whisper One TeamWhisper One Team

You reproduce a bug for the third time. The failure is still on screen, but your next meeting starts in two minutes. Say what you just did into an unsent draft while the sequence is fresh. Then add the evidence that needs exact spelling or formatting before you open the ticket.

A useful report lets a teammate repeat the same test without asking which screen you meant or what happened before the error. This workflow uses voice for the narrative and the keyboard for details that must match the source.

Start the draft with the state you tested

Open a scratch note or an unsent issue. Leave the failing window where it is, especially if you might lose the state by refreshing. Start with the conditions that matter: account role, page, build or environment, and anything you switched on before the test. Include conditions you actually checked.

For example, say: “I was in the test workspace as an editor. The project already had one attachment. I opened the attachments panel from the project page.” That gives your teammate a starting state. A phrase like “the upload thing is broken” leaves them to reconstruct it.

If the failure happened in a live account, reproduce it with test data when you can. Describe the shape of the data, such as an attachment over a size limit, without dictating the contents of a customer file. Check your team's rules before entering work details into a cloud tool. The dictation privacy checklist can help you decide what to leave out.

Speak the path in the order it happened

Say one action at a time. Use button labels that someone can find on screen. If the order matters, break the recording into short sections and turn the resulting sentences into numbered steps.

Here is a fictional example for a file upload issue:

  1. Open the attachments panel on a project that already has one attachment.
  2. Select a second file and wait until the progress indicator finishes.
  3. Close the panel without navigating away from the project.
  4. Reopen the panel and compare the two rows.

In the draft, separate what you expected from what you saw: “Expected: Both filenames remain visible. Observed: The second row is present, but its filename is blank until I reload the page.” If reloading restores the name, write that down. It may help your teammate decide where to look first.

Say how often you tried the sequence only if you kept count. “Observed in two of three attempts on the same build” is more useful than “randomly happens.” If you tested one attempt, say so. Put suspected causes in a separate note so the reader can distinguish a theory from a result.

Add exact values from the source

Copy the build number from the app, the error text from the relevant screen, and a safe test path from your notes. Use inline code for identifiers and preserve line breaks in short log excerpts. Dictating a long UUID or reciting punctuation creates another piece of text you have to compare character by character.

For a screenshot, crop to the state you want to show and check the edges for account names, private tabs, notifications and customer information. For logs, use the smallest approved excerpt that shows the relevant event. If the issue needs evidence that belongs in a restricted system, point authorized teammates there instead of attaching it to a public tracker.

Read the ticket as if you were on call

Look at the title first. “Second attachment loses its filename when panel reopens” says where to start. Then follow the steps in a fresh test session if it is safe to do so. Check whether the ticket says which role to use, how to tell the test reached the failure, and whether anything was reset between attempts.

If you cannot reproduce it again, keep the first observation and say what changed during the second attempt. A report can still be useful when it narrows the conditions. Ask the next person to check a specific remaining question, such as whether the blank row also appears for a viewer, rather than asking them to “take a look.”

To practice, choose a made-up bug and dictate the setup and steps into Notes. On an eligible Mac, download Whisper One, sign in, and follow the quick start. Review the draft, add exact values yourself, and submit the ticket when it is ready.