Dictate an issue title separately from its description

Voice Pad pairs physical shortcut controls with a supplied microphone for a configured transcription workflow. An issue title and its description need different kinds of writing. Capturing them separately can help keep the title concise while leaving room for evidence in the body. The recording software and active field determine where text goes, so inspect the destination at each transition.

What belongs in the title?

Summarise the specific behaviour or requested change in a short, identifiable phrase. Include the affected feature when that distinguishes the issue from similar reports. Leave the full history and reproduction sequence for the description instead of trying to compress an entire spoken narrative into the title field.

Dictate a draft, stop capture and edit it before moving on. Speech can leave filler or a self-correction that makes the title longer than intended. Verify exact product labels or identifiers from the source rather than trusting a plausible transcription.

How should the description be organised?

Start with the relevant context and then describe the steps, observed result and expected result. For a feature request, state the user need and desired behaviour. Keep an untested explanation labelled as a hypothesis rather than presenting it as the established cause.

Speak one section at a time if that makes editing easier. Use formatting commands supported by the transcription tool or add structure with the keyboard afterward. The value comes from a reproducible account, not from entering every character by voice.

How do you move safely between fields?

Stop recording before selecting the next destination unless the software's behaviour has been established for that transition. Click or focus the intended field and use a neutral check if the insertion point is uncertain. Some tools deliver text after processing, which can outlast the recording step.

Inspect the keypad mapping for a trailing Enter or submission action. Ending capture should not unexpectedly publish an unfinished issue. Keep final submission deliberate and visible while you review the combined title, body and any attachments.

What should the final review check?

Read the title against the body to confirm they describe the same task. Check versions, filenames, quoted errors and the order of steps. Remove private information that is irrelevant to the issue and inspect attached evidence through the normal sharing process.

The Voice Pad product details describe the input package. A reliable issue-drafting workflow separates the concise summary from the detailed evidence, with field focus and final review handled explicitly by the person preparing the report.