1. Open the exact Jira field before speaking
Atlassian currently documents C for opening Create and M for quickly adding a comment to a selected work item when Jira keyboard shortcuts are enabled. Those navigation shortcuts do not transcribe speech; they only help reach the intended editor.
Focus the exact Title, Description, or comment field. Jira’s current Quick Create calls the field Title, while Atlassian notes that it was previously labelled Summary and that JQL, API, and automation references to `summary` still work. Keep the short title separate from the detailed description.
- Confirm the Jira site, space, and work type.
- Focus Title, Description, or the intended comment field.
- Stop Dictation before moving among fields.
2. Use system Dictation as text input, not Jira automation
Start the current macOS Dictation shortcut after the insertion point is visible. Speak, stop Dictation, and confirm the transcript landed in the selected Jira field. Ordinary system Dictation does not choose the space, work type, assignee, priority, sprint, due date, labels, security level, or final workflow transition.
Website microphone permission belongs to a browser feature that directly captures audio. System Dictation is a separate Mac input path. If your organization uses a third-party voice app or Marketplace integration, its processor, permissions, retention, and administrator approval remain a separate trust decision.
3. Turn a spoken report into a useful work item
A useful bug or task needs more than a transcript. Review the title, context, observed behavior, expected behavior, reproduction steps, impact, environment, evidence, acceptance criteria, dependencies, and owner-sensitive fields before Create.
Atlassian’s current editor supports rich text, code snippets, tables, pasted images, slash commands, and Markdown conversion in descriptions and comments. Dictate prose first, then verify exact URLs, commands, code blocks, versions, dates, numbers, names, and Markdown rather than trusting speech recognition with structured syntax.
4. Inspect pre-populated, inherited, and restricted fields
Jira Quick Create can show required and optional fields from the space configuration, and Atlassian says some fields can be pre-populated from configuration or creation history. Board or inline creation can also inherit values from the current filter, grouping, or parent context.
Before Create, check the selected space, work type, parent, assignee, priority, sprint, labels, due date, security restriction, and every required field. A fluent transcript is not evidence that metadata or access is correct.
5. Keep Dictation, Rovo, and slash commands separate
Atlassian documents Rovo as a separate AI path that can suggest work items for review, refinement, and creation from a prompt or linked content. The editor’s slash command also inserts elements and can invoke Rovo where available.
System Dictation only supplies text to the focused field. It does not silently call Rovo, create linked work, search similar items, update several work items, or run Jira Automation. If you choose an AI or automation path, review its generated fields and actions under the organization’s current policy.
6. Troubleshoot focus, permissions, and shortcut conflicts
If Dictation fails everywhere, test one sentence in TextEdit and follow Apple’s checks for Keyboard settings, shortcut, language, microphone, Voice Control, and connectivity. If TextEdit works, system recognition is available.
If only Jira fails, confirm that the field is editable, your account has the required Create or Edit permission, and focus remains in the field. Atlassian notes that keyboard shortcuts can depend on the operating system, browser, permissions, installed applications, and third-party integrations. Open Jira’s `?` shortcut dialog and resolve any conflict rather than changing unrelated microphone access.
7. Add IraVoice only for local recognition or a reviewable brief
Use macOS Dictation first for an occasional title, description, or status comment. Use organization-approved Jira, Rovo, or Marketplace paths when their automation and data boundary are the intended workflow.
IraVoice 0.7.1 is the separate option for macOS 26+ Apple-silicon Macs when recognition and supported formatting should run on the Mac across supported fields, or when a longer spoken bug, story, or task should become reviewable Markdown first. IraVoice does not sign in to Jira, read work-item context, select a space or work type, populate metadata, call Rovo, apply restrictions, press Create, transition work, or notify teammates.