We plan our sprint capacity in story points - so for example we have 20 points available when planning a sprint.
When we have stories which were not completed in the previous sprint, we generally roll them over. But what was originally a 5 point story might be almost complete. If we simply move it across then it takes up 5 points, when it might now only represent 1 point, which throws off the planning.
So we looked at re-estimating the story points when rolling over the story - but now we are changing the story points which will (we assume) lead to inaccuracies in the historic sprint metrics.
Is there a general best practice and anything specific to Azure DevOps' implementation to help us with this scenario?