Rovo Says 50 Users Found. You Have 500. Here’s the Fix

[#1]

If you asked Rovo “how many users in group jira-software-users” and got back 50, you hit the built-in limit. Rovo caps user search results at 50. It also samples Jira issues around 100 to 200.

That means reports are incomplete and random each run.

The fix: Use Forge for the counting, Rovo for the writing

Build a Forge Action called get-group-members-full. It calls the Admin API with pagination and returns the real count.
Your Rovo agent uses that Action first. Example prompt: First call get-group-members-full for group jira-software-users. Then write a summary of license risk.
Rovo never sees 50 items. It sees one number: 523. Then it writes.
Why this works
Forge runs as code. No 50 item limit. Rovo handles judgment and communication. You get deterministic data with human-readable output.

Gotcha
Your Forge app needs Org Admin consent to read all users. Without it, you’re back to 50. Get approval before you promise results.

If you’re stuck on the 50 user limit, reply with your use case. I’ll share the Forge code.

[Darryl Lee]

Hey @HEMANT SAINI - This sounds like a solid approach. I'd love to see your code as I've not tried writing Forge Actions for Rovo.

I recently built some Forge Automation Actions that hit APIs to lookup groups of a user, grant Jira and Confluence permissions, etc.

[Jordi Romera]

Hello @HEMANT SAINI Could you please share how did you build this Forge action? It's amazing!