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

Forecast: Needed capacity total sum calculation displays different value for different user

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • No

      Issue Summary

      NeededCapacit in 'Plan Capacity' value should just consider just one value for the Forecast and this should be the Capability MWs or Product Bundle MWs (per Page configuration) and not the SUM of all. Logically it doesn't make sense to include all 3.

      The same value displays differently for users with a Super Admin role and different for users with a non-super admin role.

      Total estimation displays more value for non-super admin user.

      Steps to Reproduce

      1. Step 1 - Configure work item hierarchy (Epic>>Capabilitty>>Feature)
      2. Step 2 - Set estimations for each work item
      3. Step 3 - Ensure Epic estimates are set via the forecast tab
      4. Step 4 - Run Forecast Report
      5. Step 5 - Click Plan Capacity
      6. Step 6 - Review the Needed Capacity total estimation
      7. Step 7 - Logout from UserA and login with UserB
      8. Step 8 - Needed Capacity total estimation values display different values

      Expected Results

      For all the users logged in, the below values should be displayed same irrespective of their role.

      If the view is toggled to "Epic" then Need By should only sum effort (MW or TW) allocated to epics on the page

      If the view is toggled to "Capability" then Need By should only sum effort (MW or TW) allocated to capabilities on the page

      Actual Results

      Needed Capacity = Epics (MWs) + Capabilities (MWs) + Features (MWs) Calculations isn't correct, Feature (MWs)

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              dfuller@atlassian.com Don Fuller
              37857daa0c44 Mangala Narayana
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: