Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2317

Forecast: Capacity in points is not taking decimals into consideration

XMLWordPrintable

    • 1
    • Severity 2 - Major
    • Avengers - USH7

      Issue Summary

      Forecast: Capacity in points is not taking decimals into consideration

      Steps to Reproduce

      1. Login
      2. Create Portfolio, Program, Team, Release, and Sprints(You should have 3 past and 1 ongoing Sprint).
      3. Set estimation system to Points.
      4. 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.
      5. Go to the Teams Grid.
      6. Open the Team Edit>Sprints. Notice that the Average Velocity is 13.7.
      7. Now go to the Forecast.
      8. 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

            eac07d2d8a35 Roman Koshovskyi
            rpetrunyak@atlassian.com Roman Petrunyak (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: