Why occasional Jira Server 8.5 Velocity Chart Committed mismatches with Sprint Report / Burndown

[JoelF]

In Jira Server 8.5 I am seeing variations between the starting points at start of sprint on the Burndown Report and the Committed (gray) bar on the velocity chart - but only for some teams and some sprints. 

What does the Velocity Chart include in the committed value in Jira Server 8.5? Is it only the points present at the time the Start Sprint button is pressed, or are other points included (such as stories added after sprint start or stories completed outside of sprint?) 

In cases where they don't line up, the variation can be quite large, from 15 points to over 75, and again these mismatches are scattered, so I suspect either a data corruption problem or a derivation detail - some things included in Velocity Committed on the Velocity chart that are not obvious. 

Thanks in advance,

Joel

[Petter Gonçalves]

Hello @JoelF

Thank you for reaching out.

Both the Velocity Chart and Burndown reports refer to the exact same data and amount of Story Points in your board, however, from two different perspectives.

While the Velocity chart focuses on the amount of value delivered in each sprint, the Burndown Chart shows the actual and estimated amount of work to be done point in time, not necessarily the actual sprints or issues.

You can check the documentation below for a practical example and more details about the behavior mentioned above:

Burndown reports showing different story points than other reports 

For a deep dive to better understand how each of the reports works, please refer to the documentation below:

Burndown Chart 

Velocity Chart 

Additionally to that, please check at the end of the documentation that some burndown charts can display incorrect data due to some bugs, so make sure you did not set your instance in a way that would reproduce one of the bugs mentioned there.

I hope this information helps you to analyze and understand why your reports are displaying different data and the explicit reason that is causing that mismatch.

Let us know if you have any questions.