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

Forecast Report: Duplicated points being added to Epic Forecast

    XMLWordPrintable

Details

    • 1
    • Severity 2 - Major
    • No

    Description

      Issue Summary

      On the Forecast page, when clicking the Blue Arrow on an Epic to change the number in the Estimated Column to the number in the Allocated Effort column, the number is mysteriously doubled.

      For example, in the screenshot below, when the customer clicks the Blue Arrow to change the Estimated number from 24 to 12, the number in the Estimated column instead doubles to 24. Initially, due to the doubling, it appeared that the number did not change at all.

      Steps to Reproduce

      1) Navigate to the Forecast page.
      2) Locate the Epic where the Estimated point value needs to be changed.
      3) This Epic is currently only tied to one program, one PI, and has no features tied to it:
      4) On the forecast page, click the blue arrow to update the Estimated value with the Allocated value.

      Expected Results

      The Estimated Value should update to whatever the Allocated value was. In the customer's case, the Allocated value was 12, therefore, we expected that the Estimated value should have updated to 12.

      Actual Results

      The value in the Estimated column is doubled every time. We experimented with different values in the Allocated column to verify this (for example, changing the allocated value to 6 caused the Estimated value to change to 12, etc.).

      Workaround

      No known workaround at this time, when one becomes available our product team will provide one.

      Attachments

        Issue Links

          Activity

            People

              cgottlieb@atlassian.com Caz (Inactive)
              ddortch@atlassian.com Darryl Dortch (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync