Rovo
AI that writes, summarises and rewrites work item descriptions and comments
Atlassian's AI tool inside the Jira editor. When asked, it writes new text, summarises existing text or rewrites it (tone, clarity, simpler language) in a work item's description or comments, for example drafting user stories, acceptance criteria or subtasks from a prompt. The generated text goes straight into the editor, where the user can edit or undo it; each user can choose whether its writing changes are applied automatically or reviewed first.
Where to turn off Rovo: see below.
Something wrong here? Tell us ↓
Create work items with Rovo
turns a plain-language request into a set of draft work items
The user describes in Rovo Chat what they want to achieve, optionally with a link to a work item, Confluence page or Loom video, and Rovo suggests a set of work items with summaries and descriptions on an AI-powered canvas. The user reviews and edits them there, or asks Rovo for changes, and nothing is added to the space until they select Create all. It only works once an organisation admin has turned on beta AI features, and it is being rolled out gradually.
Where to turn off Create work items with Rovo: see below.
Something wrong here? Tell us ↓
Ask AI
Rovo turns a plain-language request into a Jira search (JQL)
In the List view, the user types what they are looking for in plain language (it works best in English) and Rovo translates it into a Jira Query Language search, switching to JQL mode when the request is too complex for the basic search. It is meant for finding work items, not spaces, boards or users.
Where to turn off Ask AI: see below.
Something wrong here? Tell us ↓
Smart replies
AI-drafted comments on work items
Suggested reply buttons under a work item's comment box. On some plans with Jira's AI feature, a smart reply is a prompt for AI to draft a fuller comment or conversation starter, which the user can add to before saving. A Jira admin can turn smart replies off for everyone in the Jira instance.
Where to turn off Smart replies: see below.
Something wrong here? Tell us ↓
Rovo nudges
AI-suggested work item updates from a Loom meeting transcript
When a Loom meeting is connected to a Jira space, Rovo analyses the meeting transcript and suggests updates to work items, such as reassigning them, changing priority or status, updating the description or adding a comment. The suggestions are shown only to the person who recorded or owns the meeting, and nothing changes until they accept a suggestion. It needs Rovo AI on the Jira site and Loom AI on the Loom account.
Where to turn off Rovo nudges: see below.
Something wrong here? Tell us ↓
Agents in Jira
Rovo and third-party AI agents that work on work items
AI agents (Atlassian's own Rovo agents, agents a team builds in Studio, and third-party agents) that can be assigned a work item, mentioned in a comment, or set to start automatically when work moves into a workflow status or board column. An agent uses the work item's summary and description, may use its comments and attachments and details from other work items on the site, and produces first drafts, summaries or task output. The output is visible only to the person who triggered it until they share it; anyone moving a work item into an agent's column or status starts it.
Where to turn off Agents in Jira: see below.
Something wrong here? Tell us ↓
Jira Coding Agent
writes code from a work item and opens a pull request
An AI agent that turns a work item into working code in a cloud sandbox, using the work item and the team's knowledge from Jira, Confluence, the codebase and other sources. The user works with it to refine the generated code and then creates a pull request from the sandbox.
Where to turn off Jira Coding Agent: see below.
Something wrong here? Tell us ↓
