Version report: issues closed as duplicate

[Season Hughes]

Do all Closed issues count towards velocity on a Version Report?

I'm looking at a Version Report for my team's next release. I'm seeing the predicted release date on the Version Report is a month and a half earlier than my manual calculations.

I also see that Story Points on Completed Issues on the Version Report is 134 points higher than what I manually calculated that we actually worked on.

I suspect that this is due to some issues that are status "Closed" but that we didn't actually work on. We Closed them as Resolution: Duplicate or Resolution: Won't Fix.

Can you confirm that these issues are counting towards the velocity on the Version Report?

If so, what's a workaround for this? Should we create a status other than Closed so they don't get counted on the Version Report?

Thank you!

[KAGITHALA BABU ANVESH · Accepted solution]

Hello @Season Hughes ,

If the closed status is in "Green" like done and placed in the right most column in Jira Board. Then These story points will be burned.

To over come These, 

1. Remove Story points

OR

2. Tag these issues with another status  eg. "Cancelled" and place these in a new column in jira board. (Note : not under the right most column).

This will help you regarding story points.

Thanks,

Anvesh