Short answer: open a Jira issue in the browser or desktop client, click the Description or comment field, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak reproduction steps, acceptance criteria, and links, press the hotkey again. AICHE inserts text. You set priority, sprint, and assignee (human, Rovo, or an MCP-connected agent) in Jira.
The Problem
Jira on Cloud now centers Atlassian Rovo: semantic search across Jira, Confluence, and connectors (Slack, GitHub, Figma, and dozens more), Rovo Chat, and agents in Jira you can assign like teammates. Rovo Dev can work from an issue toward code changes (with human review). Atlassian Intelligence inside the editor can summarize or rewrite text you already wrote. Jira Automation includes a Use Rovo action to transform or summarize field content from a natural-language step prompt.
Agents and Rovo still need a dense issue: what broke, for whom, environment, logs, definition of done, and links to Confluence specs. "Fix login" assigned to Rovo wastes a run. The gap is writing that paragraph under SLA pressure.
AICHE does not assign issues, transition workflows, or invoke Rovo. It fills the text fields you would type into.
Where AICHE Helps Most
| Surface | Voice use |
|---|---|
| Issue description | User story, repro, expected vs actual, AC numbered list, links to Confluence / dashboards. |
| Comments | Investigation updates, handoff to QA, post-deploy notes. |
| Epic / initiative descriptions | Scope, milestones, out-of-scope, metrics. |
| Custom fields (text) | Risk notes, test plan, rollout steps. |
| Automation → Use Rovo | Dictate the instruction for the automation rule's Rovo step (what to summarize, format, redact). |
| Before assigning Rovo Dev | Speak the implementation brief developers (or Rovo Dev) need: files, constraints, test command. |
After dictation, use Jira's Atlassian Intelligence buttons to tighten wording if you want. Start from volume you would not have typed.
How It Works
- Open Jira Cloud (app or browser) on macOS, Windows, or Linux.
- Create or open an issue. Click Description or Add comment.
- Press ⌃+⌥+R or Ctrl+Alt+R once (toggle recording).
- Speak: summary, repro, AC, attachments you'll paste after (screenshots, log excerpts).
- Press the hotkey again. AICHE transcribes and inserts. Audio is streamed for cloud transcription, processed, and discarded immediately after processing, within 1 second. No persistent audio copy.
- Set Priority, Sprint, Components, Labels, and Assignee (person, Rovo, or agent) in Jira.
Offline: encrypted local queue, processed when online (offline mode).
User Stories and Acceptance Criteria
Speak in order: "Title: OAuth refresh fails on mobile webview." Pause. "Description: As a returning user on iOS webview …" Then AC: "Given a valid refresh token, when …" Message Ready or manual bullet formatting in Jira afterward.
Example spoken AC block: "AC1: 401 from /oauth/refresh logs invalid_grant only when clock skew exceeds 60s. AC2: Retry once with server time header. AC3: QA verifies on staging build 4.2+."
Bug Reports While You Still See The Error
Stay on the failing screen. Open Jira, focus description, hotkey: browser, OS, account tier, steps, expected, actual, frequency, relevant Sentry or CloudWatch snippet you'll paste below the insert. Developers and Rovo Dev get a searchable ticket without a Slack thread archaeology project.
Rovo, Agents, and Automation
Rovo Chat (sidebar): you can dictate the question into the chat input the same way if focus is there. AICHE inserts; Rovo searches the Teamwork Graph.
Assignable agents: when your admin enabled Agents in Jira, assigning Rovo or an MCP agent without description text guarantees vague output. Dictate first, assign second.
Rovo Dev: treat the description like a PRD mini-spec: repo, branch strategy, files in scope, tests, and "do not change" areas. Human approval still applies to proposed changes.
Automation / Use Rovo: in the rule builder, click the natural-language prompt for the Rovo action, hotkey: "Summarize {{issue.description}} into three bullets for the #incidents channel: impact, owner, next update time. Redact customer emails."
AICHE does not run Automation. It supplies the prompt text.
What You Get
- Sprint-ready tickets without 15 minutes of typing each.
- Custom Vocabulary for service names, internal codenames, epic keys.
- Same desktop hotkey in Jira, Confluence, IDE, and Slack.
Plans start at $3.99/mo (annual) with a 7-day free trial, no credit card. See pricing.
FAQ
Does AICHE assign Rovo or run agents?
No. Insert text only.
Cloud vs Data Center?
This page targets Jira Cloud Rovo and Intelligence features. Data Center AI differs by deployment; verify your admin's features.
Will dictation format Jira markup?
AICHE inserts plain text. Use Jira toolbar or wiki markup after insert.
What happens to audio?
Audio is streamed for cloud transcription, processed, and discarded immediately after processing, within 1 second. No persistent audio copy.
Related Features
Try it now: open your flimsiest backlog ticket, dictate a full description and three acceptance criteria, then decide whether a human or Rovo should own it.