nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Exploring Atlassian Rovo AI – Experiences, Tips, and Challenges

M Chandra Shekar

Hi Community,

I’m exploring Atlassian Rovo AI in Jira and I’m curious to hear from others about their experiences. A few things I’m particularly interested in:

1. How teams are leveraging Rovo for workflow automation, ticket triaging, or content generation.

2. Any best practices for custom agents and keeping them permission-safe.

3. Feedback on accuracy, reliability, and guardrails — have you noticed any unexpected behavior?

4. Any tips on pricing, quotas, and managing AI usage effectively.

If you’ve used Rovo AI in your team, I’d love to hear how it’s helping (or not), and any lessons learned from implementation.

Thanks in advance!

Comments

Tracy Carlson

Hi @M Chandra Shekar This is from a recruiting standpoint, so may not be helpful to what you are looking for. Overall, where Rovo has helped the most is reducing “busy work” (summarizing, drafting, searching) so we can spend more time on judgment-heavy tasks. It’s not perfect, but with clear guardrails and a verification mindset, it’s been a net positive.

Check out the Vote for your favorite Rovo-Use Cases page: #1 & #4 for Jira sepcific use cases.

#1: Turning meeting transcripts into Jira issues with a single prompt complete with details, priorities, and assignments.

#4: Build an agent that troubleshoots errors, logs Jira tickets, and guides users through testing.

Hope this helps!

Crispin Bayross

Agree with Tracy, Rovo AI has helped the most is reducing summarizing, drafting, searching, I would put this reduction of workload to up to 80%. Start with a wide-open prompt, Rovo usual gets it right the first time, then refine the prompts (max up to 4) for the requirement and the job is done.

One unexpected behavior I noticed is assumptions. Once in a Rovo reply, I knew for sure the answer was wrong, when I asked Rovo to give me supporting evidence to the reply Rovo could not, then I asked how did you get this answer, then Rovo said it assumed.

So now, I keep a standard line in my prompts "Do not assume, base on facts only, if you need to assume, call it out as an assumption at the end of the reply." (Assumptions can help with insights).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

rovo-atlassian-intelligence