By mistake I updated story point of a closed story in a closed sprint and reverted it back to original value. Now velocity chart is not considering that story point and chart is skewed up. It is considering story point as zero in the velocity chart.
Any workaround to get the original value show up in velocity chart?
To avoid this situation, my suggestions are:
1. Do not allow to edit story point after the sprint is closed.
2. Consider original value for Velocity chart regardless of story point increased/decreased.
3. Controlled Edit that only admin can modify the story point after sprint is closed (not recommended).
In order to prevent this situation from happening again, I would suggest including the Closed status in the workflow (if it is not already there) adding to it the property jira.issue.editable with value 'false'.
By the way, I once saw a screwed burndown chart just because a user had set 1,000,000 story points to a story as a joke.
After the laughs, they corrected the story points value, but as the burndown chart had to display the estimation change, it was being displayed at a scale to show up to 1 million story points, therefore, effectively making the real consumption of story points not being noticeable in a chart with such a big scale.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs