AGENT PROFILES

Rovo Agents

Atlassian · Agent builders

Configurable team agents for Jira, Confluence and connected work knowledge.

Typical tasks

Availability in Europe
Added to the catalog on Configurable team agents for Jira, Confluence and connected work knowledge.Details
01

What it does

5 features

Rovo Agents · Agent platform

Product and access

Available offering; access methods and prerequisites are described separately in this profile.

Core features

5 features from provider sources · reviewed on 26 October 2026. Availability and limitations follow below.

  • Team knowledge

    Use knowledge from Atlassian and connected apps.

    Source 1
  • Edit Jira

    Create and edit Jira work items with granted permissions.

    Source 1
  • Maintain Confluence

    Create and edit Confluence pages.

    Source 1
  • Automations

    Invoke agents in automation rules.

    Source 1
  • Configure agents

    Define specialized goals and knowledge sources.

    Source 1

Usable AI models

Fixed choice across providers

According to Atlassian, Rovo Agents run on GPT, Gemini and open models such as Llama. In Studio you set "Quick answers" or "Think deeper" per agent, and each level has a default model tested by Atlassian; the choice can change. The checked pages do not name individual models, own keys or own models.

Model families named

  • OpenAI (GPT)
  • Google (Gemini)
  • Meta (Llama, Muse)
Model choice
Automatic or your choice
Your own API key
Not stated
Router or custom endpoint
Not stated
Local models
Not stated

The rating covers the generally available main access. Documented · Sources accessed on

Atlassian: AI transparency · Atlassian: Set a reasoning tier for a Rovo agent

02

Does it fit my task?

2 practical tasks · 3 requirements and limits

A good fit if …

  • your team uses Jira or Confluence on a Standard, Premium or Enterprise cloud plan
  • agents should have their own account with an audit trail and admins should limit access and creation rights
  • you want to limit who can create agents through groups and choose knowledge sources deliberately

Less suitable if …

  • you are not on an Atlassian Cloud plan; the reviewed admin page names Standard, Premium and Enterprise
  • you need automated agents that have a person approve every write action beforehand

Editorial assessment based on provider documentation. Not a product test.

Practical tasks

Editorial examples based on documented features. No product tests performed.

01

Team knowledge

Your input
Use knowledge from Atlassian and connected apps.
Possible result
A work product for your review.
What to check
Review results and write actions before accepting them.
02

Edit Jira

Your input
Create and edit Jira work items with granted permissions.
Possible result
A work product for your review.
What to check
Review results and write actions before accepting them.
EDITORIAL EXAMPLE

Use knowledge from Atlassian and connected apps.

Your possible prompt

Organize these shared documents by topic. Create an overview with deadlines and next steps. Prepare draft replies for my approval.

Adjust the task, data and permissions.

Requirements and limits

  • Requirement

    Setup

    Eligible Atlassian Cloud subscription and enabled AI features.

    Source 1
  • Limitation

    Usage costs

    Included in eligible cloud subscriptions with credit allowances. Additional usage is listed at USD 0.01 per credit; base subscription separate.

    Source 2
  • Not yet confirmed

    Output quality

    Review results and write actions before accepting them.

    Source 1
03

Can I use it?

Availability still unclear

Europe & regional availability

Consider installation and provider access separately. A complete regional feature matrix is not published.

Reviewed scope: Product access in Germany and the EU
Reviewed on:

  • Availability still unclear

    Access and connected services

    Eligible Atlassian Cloud subscription and enabled AI features.

    Region, reason and source

    Region covered: Germany / EU

    Documented reason: The reviewed sources document no specific restriction caused by the AI Act, DMA or GDPR. Model and service access depend on country and contract.

    Official source · support.atlassian.com · Official source · www.atlassian.com

Europe and regulation explained

Accounts & permissions

Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.

Configuration covered: Rovo Agents in Atlassian Cloud (Standard, Premium or Enterprise) with Rovo Studio

Sources reviewed:

Show all 3 points
  • Documented

    Account used

    An agent acts either with the account of the person using it or with its own Atlassian account. In the first case it inherits that person's rights and changes appear under their name; in the second they are credited to the agent.

    Evidence
  • Documented

    Admin approval

    Organisation admins manage Studio access in Atlassian Administration and can limit creation rights to specific groups. The Studio settings allow permissions to be restricted.

    Evidence
  • Documented with conditions

    Data access & team sharing

    Reach depends on knowledge sources and the account choice. With an agent account, app and space admins grant access to spaces, and any person can give agents access to their own content. Agents can be shared; the page does not state the permission model for that.

    Evidence · Evidence
04

Memory and conversation continuity

2 of 6 criteria documented

Personal summary from Teamwork Graph plus explicit conversation instructions.

Rovo Agents; personal memory controls in Rovo Chat

Sources accessed:

Documentation by criterion

StoragePartly documented

Storage and scope

Rovo distinguishes an implicit activity summary and explicitly saved instructions. The specific storage backend is not named.

SelectionDocumented

Selection and timing

Teamwork Graph automatically supplies personal background; chat can save explicit remember instructions and shows an edit link.

Edit & deleteDocumented

Inspect, edit and delete

Settings and memory shows both types. Explicit entries can be edited and deleted; activity-summary edits are suggested and applied within 24 hours.

Access boundariesPartly documented

Agent and channel boundaries

Personal memories are isolated per user and Atlassian site; even admins cannot see them. Use by every custom agent is not separately guaranteed.

RetrievalPartly documented

Retrieval

Rovo uses the summary and instructions for personalization. Teamwork Graph knowledge search is distinct; technical memory selection remains unspecified.

New conversationsPartly documented

Session reset and compaction

Disabling memory prevents new explicit memories and use of existing entries. This guide does not explain behavior during conversation reset or context compaction.

05

Cost and effort

Prices as of 26 October 2026

Prices and included usage

Pricing checked

Included in eligible cloud subscriptions with credit allowances. Additional usage is listed at USD 0.01 per credit; base subscription separate.

  • Included in eligible cloud subscriptions with credit allowances. Additional usage is listed at USD 0.01 per credit; base subscription separate.

Pricing details

Setup

Eligible Atlassian Cloud subscription and enabled AI features.

Operation & oversight

Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.

Deployment covered: Rovo Agents in interactive use and in Atlassian Cloud automation rules

Sources reviewed:

Editorial assessment

For automations the choice between user and agent account is the key decision, since no confirmation takes place there. Run history and retry are not described on the reviewed pages.

Show all 6 points
  • Open in reviewed sources

    Files and working state

    The reviewed pages do not describe which files or state an agent keeps between runs. Agent conversations can be reviewed as transcripts.

    Evidence
  • Documented with conditions

    Sign-ins

    If a third-party app is not authenticated, the agent keeps working but cannot use that tool. The pages give no validity periods for connections.

    Evidence
  • Documented with conditions

    Starting further runs

    Agents run interactively with a person or in the Use agent step of an automation rule. Which triggers and schedules are available is not stated on the reviewed pages.

    Evidence
  • Documented with conditions

    Human intervention

    With interactive use, work items, pages and emails are only changed or sent after a human approves. Automations have no approval step; there an agent can be limited to read-only actions.

    Evidence
  • Documented with conditions

    Detecting errors

    With an agent account, changes appear under the agent's name and are easier to trace in audit logs. A run history or failure notifications for automations are not described on the reviewed pages.

    Evidence
  • Open in reviewed sources

    Resuming after failures

    The reviewed pages contain nothing on retrying or resuming after failures.

    Evidence
06

Evidence and open questions

2 sources · 2 open points

Open points

The reviewed sources contain no reliable information on these points. A gap says nothing about the product.

Europe: Availability still unclear

Requirements and limits: not yet confirmed

Sources and evidence

Official sources reviewed. Example tasks are editorial suggestions; hands-on testing is outstanding.

Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.

Read profile as Markdown

How we assess the sources

Provider

Configurable team agents for Jira, Confluence and connected work knowledge.

Operator
Atlassian
Organization
Provider
Provider sourcesSource 1 Source 2 Reviewed
Changes to this profile 1
  • Configurable team agents for Jira, Confluence and connected work knowledge.

These notes describe editorial changes. Source and pricing review dates appear in their respective sections.