Back to Blog

What Is Atlassian Rovo? Features, Governance and Rollout

5 min read
Deepshikha
What Is Atlassian Rovo? Features, Governance and Rollout

“Why did we move this feature out of the release?” The Jira ticket shows the new date. The customer feedback sits in a service request. The decision and its rationale live in Confluence. For a product owner preparing a stakeholder update, finding those three pieces can take longer than writing the update itself.

That’s the kind of question I’d use to evaluate Atlassian Rovo. Can someone on the team find the decision, trace it to the original discussion and explain it accurately?

What does Atlassian Rovo do?

Rovo brings AI search, chat and agents to work recorded in Atlassian Cloud and connected tools. A team member can search for the decision page, ask a follow-up question about the related tickets and use the sources to draft a release update. What they can retrieve depends on which sources are connected and what they have permission to see. Atlassian’s overview of Rovo

Which Rovo feature fits the job?

Capability Example for a delivery team
Search Find the Confluence decision record and related Jira work items using a question in everyday language.
Chat Ask what changed since the last sprint review, then open the cited material to check the explanation.
Agents and Studio Configure an agent with instructions and relevant knowledge to draft recurring release updates for a product owner to review.
Confluence Remix Turn an existing page into a different presentation format for a stakeholder discussion.
Rovo Dev Bring AI assistance into development tasks such as planning a code change or reviewing a pull request. Check its separate entitlement when scoping a pilot.

Explore Rovo features · Rovo Dev

How the Teamwork Graph connects the evidence

The Teamwork Graph connects people, work items and knowledge across Atlassian and supported third-party tools. In the release example, a relationship between a Jira item and a Confluence page gives Rovo context for finding the decision behind a date change. Someone still needs to record that decision. If the team agreed to defer the feature during a call and only changed the due date, the ticket alone tells you when the plan changed. The reason is still an open question. Atlassian Teamwork Graph

Decide who can see information and who can act

  • App access. Organization administrators can manage Rovo access for supported apps. Some features are shared across Jira-family apps on a site, so check the effect of blocking one app while another remains enabled. Manage Rovo access
  • Source permissions. Before connecting a repository, try a representative question as a team member with typical access. Check that they can open the evidence behind the answer. Review who can read each source, especially old spaces with broad sharing.
  • External AI tools. Connecting a source for Rovo to search and allowing an external AI client to interact with Atlassian are separate decisions. For an MCP connection, identify the client, the users who can authorize it and the actions you intend to allow. Atlassian MCP Server
  • Human review. For an initial pilot, let an agent draft a stakeholder update. Give the product owner responsibility for checking dates, commitments and sources before sending it.

What does your plan include?

Atlassian lists Rovo for supported Cloud apps on Standard, Premium and Enterprise. Your app mix and plan affect credit allowances, and individual capabilities can have additional requirements. Before budgeting for a service desk rollout, check the virtual service agent entitlement and expected usage separately. For a search pilot, start with the apps you already license and the sources your team needs. Rovo access by plan · How Rovo credits work

Run a pilot around one recurring question

  1. Choose a workflow and a baseline. Ask one product team to prepare its usual release update. Record how long it takes to find the rationale for three scope changes and who they need to ask.
  2. Prepare the sources. Select the Jira project and Confluence space, identify the decision owner, and archive or clearly mark superseded pages. Agree on which source takes precedence when a ticket and a page disagree.
  3. Test with the intended users. Ask the same questions using Rovo. Have the decision owner check each answer against the source. Record where Rovo found the right decision, where it used an old one and where the rationale was missing altogether.
  4. Decide whether to expand. Compare preparation time and corrections with the baseline. Pair those findings with Rovo activity trends. A count of active users tells you whether people tried the tool. The reviewed updates tell you whether it helped them do the work. Rovo activity insights

Common questions

How does Rovo relate to Atlassian Intelligence? Teams may recognize Atlassian Intelligence as the name attached to earlier in-app features such as page summaries. Atlassian now describes AI experiences inside its apps under Rovo as well. Rovo also includes cross-tool search, chat and agents. AI in Atlassian apps

Do we need developers to build an agent? Teams can start in Studio with a no-code agent. For a release-update draft, the first design decisions are which sources it should use, what the draft must contain and who reviews it.

Why does Rovo keep surfacing the wrong answer? Pick one example and follow its sources. Check whether the current decision was recorded, whether the requester can read it and whether an older page still looks authoritative. Those checks help distinguish a content problem from a permissions or retrieval problem.