What’s the Most Surprising Way You’ve Used Rovo or Atlassian AI?

[Peter Lovas]

Hey everyone! 👋

I’ve been diving deeper into how teams are adopting Rovo and the broader Atlassian AI features, and I’m really curious about one thing:

👉 What’s the most unexpected, creative, or surprisingly useful way you’ve used Rovo or AI so far?

Maybe it helped you:

• uncover insights you weren’t looking for

• clean up Jira or Confluence faster than expected

• boost communication across teams

• or just save time in a way you didn’t see coming

I’d love to hear real stories, clever hacks, or even things you tried that didn’t work as planned. 😄
Let’s compare notes and inspire each other, the fun use cases often come from the community!

Looking forward to your ideas!

[Mariano Tallarico _Appricity_]

Currently, my team and I are using Rovo in two ways that, although they seem quite different, ended up complementing each other far better than we expected. On one hand, we're leveraging it on the customer-facing side, especially in our portals. It has become the first line of support in our service desks: it provides initial responses, guides users through processes, and even resolves simple requests without any human intervention. And even when it can’t fully close an issue, it still leaves everything far more organized and categorized, which speeds up our team’s work significantly.
The truth is that many of those everyday, repetitive questions that used to eat up our time are now being solved in seconds by Rovo.

On the other hand, we’ve also started using it internally as a sort of permanent tutor for our Jira administrators. We’re documenting every process in Confluence —both the ones we’re currently implementing and the ones we’ve built for past clients— so Rovo can directly answer how each configuration works, what automations a project has, how user management is handled, or any typical onboarding question. Our long-term vision is to delegate more and more of the basic admin tasks to Rovo: user provisioning and deactivation, license assignments, minor configurations, everyday maintenance… everything that currently takes time but doesn’t require creativity or deep analysis.

This would allow us to spend more hours designing solutions, improving processes, and delivering real value to our clients, while Rovo takes over the more repetitive work. And the best part is that we’re already seeing the benefits: less operational noise, less wasted time, and a stronger focus on what truly matters.

[Ryan Boyd]

Image recognition here. 

We ran Rovo against server room standards and generated a punch list of remediation tasks from a group of images. More on that here. https://www.linkedin.com/pulse/rovo-image-recognition-ryan-boyd-nbctc/

We are also using it's object character recognition abilities to reduce a ton of manual/swivel chair work. Submit this doc or group of docs and get a structured table to move into another system or screen. It's increased speed and accuracy across the board. 

[Susan Waldrip]

We use JSM Standard so won't have Atlassian Intelligence for general use. While it's free to use now, I'm using Ask Rovo (Rovo Chat) to answer questions about how to configure things in JSM, especially when I can think of more than one way so Rovo provides options and pro's and con's for all. It's been helpful so far.