-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 10.82
-
Component/s: reports - forecast
-
1
-
Severity 2 - Major
-
Avengers - USH7
-
None
Issue Summary
Forecast: Capacity in points is not taking decimals into consideration
Steps to Reproduce
- Login
- Create Portfolio, Program, Team, Release, and Sprints(You should have 3 past and 1 ongoing Sprint).
- Set estimation system to Points.
- Add Story with 1 Point LOE to one past Sprint. Add Story with 32 Points LOE to the second past Sprint. Add Story with 8 Points LOE to the third past Sprint. Accept Stories. Mark Sprints completed.
- Go to the Teams Grid.
- Open the Team Edit>Sprints. Notice that the Average Velocity is 13.7.
- Now go to the Forecast.
- Check the Capacity for the Team.
Expected Results
Capacity is calculated as Average Velocity*number of Sprints that team has in the selected Release. In our case, 13.7*4=54.8, rounded to 55.
Actual Results
Capacity calculations are not taking Decimals into consideration. In our case 13*4=52.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- resolves
-
ALIGNSP-6951 Loading...