Is this really ready for Prime Time? Confluence Rovo usage is particularly terrible

Jo-Lee Bertrand

I attempted to use Rovo to help me do some SIMPLE tasks in Confluence (rename a chart, etc.).  Tried for about 2 hours. Gave up in mass frustration. 90% of the responses were not even factual. Maybe Atlassian needs to hire back those folk it let go and let Rovo go...Sheesh.

Ajay _view26_

Hi @Jo-Lee Bertrand 

Rovo's capabilities within Confluence is still maturing, and there's a meaningful gap between what people expect from an AI assistant embedded in a productivity tool and what it can reliably deliver today.

A few things worth knowing:

What Rovo is currently good at in Confluence:

• Searching across your instance and summarizing content from multiple pages.
• Answering questions about your Confluence content (e.g., "what's our refund policy?" if it's documented somewhere).
• Drafting new content or expanding on bullet points.

Where it struggles (and where your frustration likely came from):

• Direct manipulation of page elements (renaming a chart, reformatting a table, moving sections around) is either not supported or very unreliable. Rovo is primarily a search-and-generate tool right now, not a page editor. It can suggest edits, but it doesn't have the fine-grained control to modify embedded macros or chart titles directly.
• Factual accuracy about how to do things in Confluence is hit-or-miss. It can hallucinate menu paths, button names, or settings that don't exist in the current UI.

For structural/formatting tasks (renaming charts, adjusting macros), you're better off editing the page directly. Rovo isn't wired into the macro layer yet in a way that's reliable.

For search and knowledge retrieval across your space, it's genuinely useful — that's where it shines.