Deleted Story points still showing on Sprint Burnup Chart

Question

I've deleted a story from the Sprint and replaced it with another that had the same amount of story points. My burnup chart is now showing both points, being one of them has been deleted.

What would be the best way to approach this problem? Should I try to undo the deleted issue and then change the points to 0.1 (since 0 does not change the burnup either from my experience)? My company has OKRs of predictability and estimated versus delivered Story points is one of them.

Thais Faria · Answer

From a user standpoint, I believe that deleting an issue from an active Sprint is usually done because you've changed the points to something that was more important at that time. I've changed scope but not effort. Is it possible to change the "delete issue" experience to, when this issue is on an active Sprint, prompt the user requesting if it wants the issue to be removed from Sprint before deleting it? It would really help

Thais Faria · Answer

I would like to know if it is still not possible to restore deleted issues. We've run into the same problem again and it's messing up our metrics :/

Earl McCutcheon · Answer

Hello @Thais Faria ,

Thanks for reaching out, and when it comes to removing an issue from an active sprint the reports are designed to show the committed story points at the start of the sprint against what was completed.  So the behavior you are describing is expected, as the commitment was made when the sprint was started so removing issues is expected to sho up as scope creep.

When you remove an issue from a sprint via a drag and drop from the sprint to the backlog or click on the issue key in board so that the detail pane pops up. On the detail pane, click the three dot option menu on the right or right clicking the issue and selecting "Remove from Sprint" the reporting is going to show that the issue was removed as the points were committed to the sprint at start.

During sprint planning the best approach is to verify the issue are going to be completed during the sprint, but if the issue is not completed on time during the sprint that data is held on to and reflected in the reporting to show which items were overcommitted in the previous sprint to track scope creep so that you and your teams can adjust planning to compensate for the next sprint planning session.

However if you fully delete the issue entirely from Jira the data the reports are pulling from lives in that issue, so once deleted the data is removed from the board reports, and will no longer show as issues removed from sprint.  So if you did need to entirely remove the committed data for an adjustment create a new issue containing the same details as the original, then delete the original, noting all comments and work-log history will be lost in this process, and you would need to redo all estimation manually.

Regards,
Earl