How do you use Rovo as an Atlassian admin?

[Dorin_Goldin]

Hi everyone 👋

We’ve recently started exploring Rovo within our organization, and I’m curious to learn how other Atlassian admins are leveraging it for their teams.

Our first use case is using Rovo as a smart assistant for handling advanced user tickets. The idea is to help our team quickly gather relevant information from all internal sources—Confluence, Jira, Slack, and other tools—so they can resolve complex issues faster and more efficiently.

I'd love to hear:

• What use cases have you implemented with Rovo?
• Any tips or best practices for integrating it with Atlassian products?
• Challenges you've faced or things to watch out for?

Thanks in advance for sharing your experiences!

[Jaime Escribano (knowmad mood)]

Hi Doring, welcome to the community!

With Rovo, I was able to set up an automation that has saved a significant amount of time for our senior developers.

Atlassian includes the agent "Readiness Checker" which is meant to give feedback on whether or not an issue is OK to start working on by referencing some quality criteria:

- Clear and actionable description

- References to documentation 

- Estimation, either story points or hours.

As of now, before an issue can be added to the sprint, they need to be reviewed by the project's System Architect. He has to ensure it meets our quality standards. But this can take a lot of time and back and forth, especially with junior profiles.

My company duplicated the agent and added some more criteria of our own.

Then, we created an automation that follows this logic:

- When a ticket is moved to "ready for sprint review"

- Rovo Agent "Readiness Checker" with the promt "Review the {{triggerIssue}} and provide feedback on whether or not it is read"
- If Smart Value condition: {{Agent Response}} contains "Not Ready" 

          - Transition the issue back to "To Do"

- Else

          - Transition the issue to "Ready for Sprint"

Then: add a comment with the Rovo Response.

This is great, cause the Agent provides unambiguous feedback on whether or not the issue is ready, and our juniors learn in no time how to get through the approval process. This is now fast, easy, and does not stop our high-value seniors with low-value tasks.

It meets the criteria of repetitive and low risk, so it's perfect for AI automation.

I wonder if we should do something similar for our Confluence documentation? :D

----

As per recommendations, I would recommend going through this learning path. It's short, sweet and has valuable insight on how to properly prompt the tool.

Lastly, look into the Rovo discussion group! There are discussions daily on use cases and tips from the community.

Regards,

Jaime

[Benjamin]

Hi @Dorin_Goldin 

Welcome. Also, relatively new to Rovo. So far, the main thing is the KB content and making sure it's well maintain...So that rovo search can provide the right data to the end users. The results is going to based on how accurate the content is. 

The new feature is what seems more interesting for admins is the Rovo studio app. Looks like automation, assets, agents, can be built with no code. Looking forward to testing this out.

https://www.atlassian.com/blog/announcements/team25-rovo-for-all

[Dorin_Goldin]

Thank you @Benjamin :)

Great idea we are planning on maintaining our user KB this way.

Have you encountered any issues with that use case?