A few days ago, I earned the Atlassian Rovo Fundamentals certification (ACH-800).
In preparing for the certification I realised something, Rovo will change the way teams use Atlassian. I gained clarity about where Atlassian is heading next.
I’ve spent years working with Jira, Confluence, and Jira Service Management across different industries. I’ve seen how teams rely on these tools to organize chaos, manage delivery, and connect their work.
Atlassian’s integration of Rovo feels very intentional. It’s integrated in a way that makes it more than just another feature or add-on. It completely overhauls how Atlassian tools think and connect.
Rovo: Atlassian’s Bold Revolution
Atlassian has always been strong on structure; issues, pages, workflows, requests. But structure alone doesn’t create understanding or reduce time spent to complete tasks.
Teams still lose time searching for the right context: the Confluence page linked to a Jira epic, the incident that connects to a past root cause analysis, the customer request that ties back to a known bug.
Rovo steps right into that gap.It’s Atlassian’s new AI-powered layer built directly into Jira, Confluence, and JSM.
You can read more about what Rovo is here
It’s not only pulling data but it understands relationships between that data.
When you ask Rovo a question, it doesn’t return a list of results; it gives you the answer that fits the context of your work. And I think that is very important.
In short, Rovo turns the Atlassian Cloud products into something that is a more cohesive system that recognizes patterns, connects the dots, and helps teams work smarter and faster.
Inside the Certification
The ACH-800 exam is built for new and growing Rovo users. Here are the specifics:
- Core skills demonstrated: Use knowledge cards for instant insights, use the Rovo Chrome extension, identify common use cases and use Rovo Agents, create generative AI prompts using the TCREI framework, tailor responses by analyzing query details, recognize app-permission implications on search results, and browse Rovo Chat history to retrieve prior conversations.
- Exam breakdown: Rovo basic operations — 39%, Agents — 23%, Chat — 18%, Search — 20%.
- Logistics: Up to 20 questions, 45 minutes, passing score 70%, free to take, non-proctored online, certificate valid for 12 months (renew by retaking the free exam).
That structure matters because it tells you what Atlassian expects people to do with Rovo not just what buttons to press. It’s practical: search, chat, agents, prompts, permissions, and history.
A practical starter checklist (what I did before the exam)
- Install and test the Rovo Chrome extension across a sample workflow.
- Create one simple Agent for incident post-mortems (summarizes related tickets and finds prior RCA).
- Convert three frequently asked Confluence pages into knowledge-card-ready pages (clear title, TL;DR, links to related tickets).
- Review app permissions and run a search test to see what changes when permissions are restricted.
Small actions like these get real wins quickly. They’re low effort, high value.
Beyond AI: Why Rovo Matters
We’ve all seen AI hype before. But what Atlassian is building with Rovo is less about “AI” and more about relevance.
If you’ve ever had to dig through Confluence just to find a link that explains an obscure Jira field, or tried to remember the title of that one incident report from last quarter — Rovo is built to end that.
For admins, it means faster discovery and fewer repetitive questions.
For developers, it means connecting documentation, tickets, and dependencies in real time.
For teams, it means moving from “Where is that?” to “Here’s what we need.”
Rovo is not replacing expertise but rather amplifying it. It gives everyone in the team the ability to act with context not just data.
What this means for Atlassian professionals
If you build, administer, or consult on Atlassian systems, Rovo changes your priorities. This is the time to start learning Rovo early.
- Documentation and structure matter more. Rovo can only connect things that exist. Make documentation linkable, taggable, and practical.
- Design for intent. Think about how people will ask for help. That determines whether a knowledge card or an Agent will solve the problem.
- Permissions change outcomes. The exam highlights how app permissions affect search results. That’s a governance problem as much as a UX one — you need to get permissions right or Rovo will simply surface the wrong context.
Rovo changes how knowledge flows inside organizations.
It changes what “search” means.
It changes how teams document, troubleshoot, and even onboard.
Learning Rovo now is not the trendy thing alone, it has become foundational. It’s about understanding a new interface for knowledge inside Atlassian Cloud. If you know how to structure content, how to create useful Agents, and how to shape prompts, you’ll help teams stop asking “where is that?” and start acting faster.
Understanding Rovo today gives you an advantage tomorrow. Not just in implementing it but also in designing better systems around it.
And that is where the value lies for those of us who build, maintain, and extend Atlassian environments every day.
Certification to Vision
For me, earning the Rovo Fundamentals certification is more about staying close to the evolution of the tools I’ve built my career around. The Rovo Fundamentals cert validates the skills Atlassian expects you to use: search, chat, agents, prompts, and permissions. That’s a useful map for anyone who manages Atlassian environments.
Rovo is Atlassian’s first major step into a world where AI is major part of all activities. Where in companies context matters more than content and systems can finally understand the relationships between tickets, pages, and people.
For me, the main value is not the certification but it’s the shift in how I see work inside Atlassian: from isolated artifacts (tickets, pages) to connected context that helps people act. If you build with that in mind, you’ll stop treating Rovo as a feature and start building systems that actually make teams faster and less frustrated.
And that’s exciting to me.
Because it means the tools we use are growing closer to how we collaborate in real life.
Stay Clouding!
