Velocity Report committed points are not calculated correctly...

[Oscar Foley Praderas]

My Jira version is: Jira v8.21.1

In sprint #31 I have some tasks that are descoped. The number of points of these descoped tasks is 55. 

Then I finish Sprint #31 and start Sprint #32. That brings automatically those descoped tasks into sprint (I think it shouldn't.,. but for whatever the reason they are in)

So the day that Sprint #32 starts it has 63 points. Later during the sprint I've changed scope by adding two tasks for 11 points.... for a total of 74 points.

Then I close the Sprint #32 with with 66 finished points and 8 points not finished...

When I look at the burndown chart of sprint #32 everything is fine.

You can see that:

- We committed to 74 points (red arrow).
- There was 8 points not finished. (green arrow)
- The descoped tasks are visible, but despite having points, ther are seen as 0 points.

But when I look at the velocity report::

- The completed points value is correct: 66 points
- The committed points value is wrong: It is 129 points
- We really commited to 74 points so 129-74 is 55 points. Those 55 are the number of points of descoped tasks.

So what is the bug?

It seems to be 2 bugs here:

1- In Velocity Chart Report... if, for whatever reason, we brought descoped tasks into the sprint..  their point values shouldn't be used for calculation. Velocity reports should behave as the other reports like Burndown Chart Report, that doesn't count he size values for the report.

2- When finishing a sprint and creating  next one... descoped tasks shouldn't be brought to next sprint. Descoped should be treated as Done.

[Danut M _StonikByte_]

Hi @Oscar Foley Praderas,

This might be a bug in the Jira reports. We also observed issues like this along the time... You could report it to Atlassian, so they can take a look.

Alternatively, you could try our Great Gadgets app. It offers many gadgets including Velocity, Sprint Burndown and Release Burndown that calculate differently than Jira reports. It might offer correct results and solve this issue for you.

 If you have questions, please don't hesitate to contact us at support@stonikbyte.com. 

Thank you,

Danut M.