What's in your Rovo? Let us know for some swag!

[#1]

Hey there, Community! As a newlassian, it’s been so amazing to see all the ways folks have been using Rovo the past three months. We even coined a spin-off term inspired by IYKYK–if you Rovo, you know (or IYRYK for short) because whether you’re getting project updates or catching up after vacation, Rovo is the easiest way to find the internal knowledge you’re looking for… fast ✨ 

I know that Community is always finding innovative things to do with our products, so I wanted to host a little brag-fest to see what you have all been up to on Rovo 👀 

Here’s how to share what you’ve been doing with Rovo thus far (and potentially win some really cool prizes! 🙌

🎯 How to Participate:

1. Share your top tip or trick for using Rovo: What cool ways are your teams using Rovo? How have you made it work for your needs? We want to know how you've capitalized on Rovo’s abilities, and the tips and tricks you wish you’d known as a new user.

2. Got a unique Rovo agent on your team? Tell us about them!: If you’ve got Rovo Agents – whether they’re built-in or your own custom creations – we’d love to hear how they’ve been helping your team shine. Share the scoop on how you brought Rovo into your workflow, what problem you were tackling, and all the awesome ways Rovo has helped you out.

3. To join in, just comment, link to a public Confluence page, or record a Loom: Get creative! Whether it’s a detailed comment about how you’ve made the most of Rovo’s brainstorming skills, a link to a stunning Confluence page showing off your custom Rovo agent, or a Loom video of Rovo in action, we want to see it all. Plus, you’ll snag the Rovo Visionary Community Badge and 75 Kudos when you leave a submission.

                                                   

When can you participate? NOW!!! From August 6th at 1:30 PM PST to August 13th at 11:59 PM PST

But wait... there’s more! 😱

Everyone who joins in will be entered to win some super cool prizes! 👀

🏆 Prizes:

• 3 lucky winners will snag an exclusive Atlassian swag box! 🎉💙

• 3 more winners will get a $20 electronic gift card to treat themselves! 🥳

Note: all winners will be chosen at random and will need a personal email they can access in order to be able to receive one of the prizes.

We can’t wait to hear all the fun and creative ways you and your teams have been using Rovo – and to show that if you Rovo, you know!

[Marc Solomon]

RFI Assist Rovo Agent: Flagging Likely Variations from Incoming Emails in Confluence

Hi everyone,

We’ve built a smart agent inside our Atlassian environment called RFI Assist, designed to help project teams identify potential variations by analysing emails that are imported into Confluence via API.

Workflow Overview

• Project-related emails are automatically loaded into Confluence pages via API.
• Each Confluence page is linked to a related Jira work item (e.g., RFI, instruction, or correspondence record).
• RFI Assist is triggered via Atlassian Automation whenever a new page is created in the relevant space.
• The agent then begins its review workflow immediately.

What the Agent Does

 Once triggered, RFI Assist:

1. Reads the content of the Confluence page, typically the body of the email.
2. Cross-references two key documents:
   
   • Contract Guidance Notes (hosted in Confluence).
   • The Scope of Deliverables from the original contract.
3. Uses a Rovo agent to interpret whether the language in the email suggests a variation, such as changes to scope, timing, or cost.
4. Leaves a comment on the page with a variation likelihood rating and links to relevant contract clauses, e.g.:
   “This communication appears to have a moderate to high likelihood of being a variation to scope. Refer to Clause 5.2 of the Contract Guidance Notes for verification.”

 Why It Matters

Variation requests are rarely explicit. They often arrive as informal assumptions or vague instructions buried in everyday emails. By pairing Confluence, Jira, and Rovo, RFI Assist provides a proactive contract awareness layer, helping teams identify risk early and avoid reactive change control.

Technical Setup

• Confluence pages are generated automatically via API ingestion of incoming project emails.
• Each page is associated with a Jira work item, creating traceability between communication and action.
• RFI Assist is powered by Atlassian Automation.
• The Rovo agent handles interpretation and makes contract-aware decisions based on live linked content.
• Final output is added as a comment directly in the Confluence page, for visibility and audit trail.

Current Challenge: Rovo Agent Processing Limits

Our only major limitation at the moment is that we’re consistently hitting the daily processing limits for Rovo agent minutes.

We receive hundreds project emails per day across the practice, each creating a new Confluence page — which RFI Assist is set to review. The current Rovo usage limits aren’t scaling with our volume, and this is beginning to affect reliability.

If anyone from Atlassian is reading this and open to discussing adjustments to Rovo quotas or alternative scaling strategies, I’d love to connect. Otherwise, we may need to explore rewriting this pipeline outside the Atlassian environment, which we’d prefer not to do if avoidable.

Happy to collaborate or swap notes if others are on a similar path.

regards

Marc 

PS: We’re part of the team at BVN helping deliver Atlassian’s new Sydney headquarters. We’re passionate about combining architectural design with digital innovation — in both buildings and tools. 🏗️💡

[Utkarsh Agarwal]

"Sprint Sage"

Our “Sprint Sage” Rovo Agent suggests story points from our own Jira history, so refinement moves twice as fast.

How it works!
It pulls the last 8–10 sprints of completed issues, looks at type, labels, and time logged, then proposes an estimate with a short rationale and confidence band right inside Rovo Chat.
We trigger it during grooming with a quick prompt like “Predict Story Points using past work” and it posts suggestions back to the ticket and our #refinement channel, so the team can accept or tweak on the spot.

Tips we wish we knew sooner:

• Normalize labels and add a tiny “estimation-notes” field—clean inputs make the agent’s suggestions much better.
• Keep estimation guidelines in a Confluence page and pin it as the agent’s knowledge source, so suggestions follow team norms automatically.
• Wire the agent into Automation to comment with its estimate when an issue enters “Refinement,” reducing manual pings.

Excited to learn other planning hacks folks are using!