Why would anyone consider them completed or want a report including them with issues actually worked and completed?
As a workaround, I tried changing the story points on cancelled issues to 0, but this still doesnt reflect in the sprint reports.
Hello @Greg Mueller
In what way exactly, and for which specific report, is changing the story points to 0 not getting you the desired result?
Any report that shows story points shows the initial point assignment in the totals. The sprint has already closed.
The initial story points total at the beginning of a sprint will not be changed by changing the story point values during the sprint.
If you want to excluded issues that end up being Cancelled and have that affect the historically recorded initial story points for a sprint, then you will need to change the filter for the board to excluded Cancelled issues from the board entirely.
It looks like there is a record of story points I have changed during the sprint. Isn't that what those arrows are indicating? The filter should meet my goal, thank you. But what is best practice for handling cancelled issues? Is it that, or to leave them in the reports?
Yes, there is a record in the sprint for changes of scope. Changes of scope include changes of story point values (or time, if you are using time for you estimation and tracking), adding issues, and removing issues.
But changing the scope during the sprint does not change the scope documented at the beginning of the sprint.
If you change the points on Cancelled issues to 0, that will be reported as a reduction in the burndown chart over time, but does not change the starting point of the chart, nor the Committed value in the Velocity chart.
If the only change in scope you had was to set a Cancelled issue from 5 points to 0 points, and if you completed all the other issues in your sprint without changing the scope, then your Completed points would be 5 less than your Committed points.
I don't have a specific suggestion on the best way to handle Cancelled issues, or other scope changes. I think it depends on how your team/company interprets the Velocity, Burndown, and other available reports when scope change impacts them. I'm sure there is.a variety of information available on the internet on the topic of best practices related to Cancelled issues.
It looks like you're new here. Sign in or register to get started.
