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!