Completed Work not matching between Burnup Chart and table

[Robert B]

I have often (but not always) observed that the number shown for completed work in the Burnup Chart of a completed sprint doesn't match the number shown in the table below the chart.

Example burnup chart showing 113 story points of completed work at the end of the sprint:

And here the corresponding table showing 100 story points of completed work at the end of the sprint:

So, which one is right: 113 or 100 story points of completed work? And why is there a mismatch between the two?

[Brant Schroeder]

@Robert Biuk-Aghai welcome to the Atlassian community

Is this happening on all sprints?  Do you have story points on anything subtasks?  

[Robert Biuk]

(Some Atlassian strangeness: login with the account which I used when making this post throws an error, so here I reply with a new account.)

As mentioned, this does not happen on all sprints. Here is a selection from the last five completed sprints in our project, with the displayed number of story points in the table vs the graph of the burnup chart:

sprint current-1: table 171 vs graph 174

sprint current-2: table 137 vs graph 138

sprint current-3: table 77 vs graph 82

sprint current-4: table 62 vs graph 67

sprint current-5: table 97 vs graph 97

So for this sample, there is a deviation between the two numbers 80% of the time. I'm sure there is a good reason why each number is at it is, perhaps because some things are considered or not considered, such as tickets resolved with "Won't do" or whatever. BUT, from a UX point of view, showing two different numbers for what should be the same thing is really, really not good. It just causes confusion and doubt in the system. Bottom line: as a user, I expect either that the same KPI is consistently shown with the same value, or else there should be two different names for two different KPIs.