ROVO Can't access basic Sprint information?

[Christopher Danner]

I was interested in seeing if ROVO could provide information similar to data we have in an EazyBI report:

• Story points committed
• Story points added
• Story points removed
• Story points changed
• Story points completed
• 5 sprint average velocity

BUT ROVO returned a message saying "I'm currently blocked from seeing the exact story point and velocity chart data via the APIs I can access..."

It's surprising to me that it wouldn't be able to access this information as this seems pretty basic - is this potentially a configuration issue?

[Rebekka Heilmann _viadee_ · Accepted solution]

Hi @Christopher Danner 

there is no direct API for any of those data points. The Sprint Report (which every Scrum Board provides without Rovo) provides those metrics but cannot be pulled from API directly. What other reporting tools do is pull in the (historical) issue data and then calculate all those metrics from that.

To my knowledge, that data is not stored in the database but always pulled and calculated on request. So Rovo would not have access to it unless you use step by step instructions on how to build the specific metric.

But then LLMs are not great for reporting anything. If you give it a report it can then analyze trends, summarize stuff, explain things. Or it will create a visual from existing numbers. But creating the metric itself involves a lot of calculating which is (so far) a bad use case.

[Dr Valeri Colon _Connect Centric_]

Hi @Christopher Danner let me rephrase and add to what @Rebekka Heilmann _viadee_ is saying - This is usually a capability limit, not your config. Rovo can read issues and fields (including story points) but it doesn’t always have access to the agile report metrics (commit/add/remove/velocity) the way eazyBI does, because those come from sprint report/board analytics APIs and history calculations. Workaround: have Rovo compute a rough version from issues in the sprint (planned vs completed) if your story points + sprint field are consistent, or keep eazyBI/Atlassian Analytics as the source for official sprint metrics.