Wrong count of workitems and estimate in response of Rovo agent

[richa bhatnagar]

I am creating a Rovo agent as sprint analyzer mainly to calculate sprint progress percent and velocity burnt as mid sprint checkpoints. I have given elaborate description and prompts but agent keeps on giving me wrong count of workitems for instance in same reponse it will give no. of user story at 5 at one place and 6 at another. In breakdown table story point estimate mentioned as 3 whereas on sprint board it's 2. 

any thing that can be done to fix it as I plan to use this agent to create views for team and stakeholders but afraid information given is wrong.

Am I going wrong anywhere? has anyone else faced this issue?

[Dr Valeri Colon _Connect Centric_]

@richa bhatnagar welcome to the community. I would not rely on a Rovo Agent alone for exact sprint counts or estimates. Agents can summarize and reason over Jira data, but they may miscount or merge context unless the source data is constrained. For stakeholder views, use Jira reports, dashboards, JQL, or automation for the numeric calculations, then have Rovo explain the results. For accuracy, ask the agent to cite the JQL/filter used and list the issue keys included in each count.

For more insights: https://community.atlassian.com/forums/Rovo-articles/Why-Does-Rovo-Struggle-with-JQL-Champions-Slack-Insider/ba-p/3210628

[Nikola Perisic]

Welcome @richa bhatnagar 

When you were creating your agent did you also tell it what to emphasize on and also what to avoid?