Work details capacity planning is based on tasks and Remaining Work, not user story points.
Key points:
- The Sprint backlog includes Work details options, including capacity bars.
- Capacity bars update when:
- work is assigned with nonzero Remaining Work
- Remaining Work changes
- dates change within the sprint
- The Remaining Work field on tasks is used by capacity charts and the sprint burndown.
- Azure Boards supports rollups for numeric fields like Story Points on product or portfolio backlogs, but team capacity can't be rolled up.
So there is no configuration to make Work details calculate team capacity from user story points. To use sprint capacity planning effectively, define tasks under the user stories and estimate those tasks with Remaining Work in hours or days. The capacity tool then compares that planned task work against each team member’s available capacity.
If the goal is to track story-point progress, use backlog rollups or the sprint Analytics burndown options, where Burndown on can be set to a sum of a field such as Story Points, Effort, or Size. That is separate from the Work details capacity calculation.