Is the Jira Velocity Report Story Point Mismatch vs API a Known Issue? Any Fix or Workaround?

[Raman_ Bhavya]

Hi

We're noticing that the Story Points Committed and Completed shown in the Jira Velocity Report do not match the totals we get when pulling the same sprint data through the Jira API (and even when loading it directly into our data lake with no transformations).

Before we explore workarounds or raise this internally, I wanted to check:
Is this discrepancy between the Velocity Report and the API a known issue in Jira Cloud?

If yes:

• Are there any recommended local fixes or practical workarounds?

• Is Atlassian planning to address this or release updated APIs/endpoints that align with the Velocity Report logic?

Appreciate any guidance or confirmation from others who have run into the same problem.

Thanks!

[Tomislav Tobijas · Accepted solution]

Hi @Raman_ Bhavya ,

I believe Velocity Report calculates "Committed" as the total estimate of all work items in the sprint at the moment the sprint begins. As for any stories added to the sprint or changes made to estimates after the sprint starts, are not included in this total.
On the other hand, "Completed" reflects the total completed estimates when the sprint ends, incl. any scope changes made after the sprint started. 👈

API data may include issues or estimates that were added or changed after the sprint started (which the Velocity Report intentionally excludes).

I guess it could be a difference in timing and inclusion criteria 👀

It also may vary if you're using company-managed and team-managed spaces (ex. projects) 

As for some plans from the Atlassian side, I've only managed to find these two relevant suggestions:

• JRACLOUD-90396: Sprint-related reports do not keep historical if the statuses are no longer available 
• JRACLOUD-94950: One story point field across team-managed projects and company-managed projects 

Hope this helps.

Cheers,
Tobi

[Raman_ Bhavya]

Hi @Tomislav Tobijas ,

Thanks, this makes sense and aligns with what we’re seeing.

Another comment on a related thread mentioned that Velocity relies on historical GreenHopper sprint snapshots, which are not fully exposed via current REST APIs, hence the mismatch when relying on issue-level API data.

Just to confirm: is this considered a known, long-standing limitation rather than something Atlassian plans to align via APIs in the near future?

Also, are there any Marketplace apps you’d recommend that reliably capture sprint start/end snapshots and closely mirror the Velocity Report logic for external reporting?

Appreciate the insights.

[Rahul_RVS]

Hi @Raman_ Bhavya 

Welcome to the community !!

If you would be interested in a mktplace app for this requirement, pls do take a look at 
Agile Velocity & Sprint Status Gadgets 

The app comes with few dashboard gadgets to track team member's / team's velocity / productivity based on story points / time spent / issue count in a sprint  and also track sprint status with multiple parameters.

Disclaimer : I am part of the team which developed this app

[Tomislav Tobijas]

Just to confirm: is this considered a known, long-standing limitation rather than something Atlassian plans to align via APIs in the near future?

@Raman_ Bhavya That's a good question. I'd say it's a known limitation, but you could reach out to Atlassian Support to have them officially confirm it.

Also, are there any Marketplace apps you’d recommend that reliably capture sprint start/end snapshots and closely mirror the Velocity Report logic for external reporting?

I'm not really an expert here, but I've found apps like:

• Agile velocity charts: gadget reports on Jira Dashboard 
• ActionableAgile® Analytics: Kanban/ Agile Metrics, Forecasts 
• Pivot Report: Roll Up Epic Issues, Worklogs & Time in Status 

Potentially, you could test those and see if they will fit 👀