Progress By Objective Report - The planned value is not reflecting in the charts

XMLWordPrintable

      Issue Summary

      In the Progress By Objective report, there are three charts exist, which are Program Increment Objective, Program Based Objective, and Team Based Objective. If an objective is created in the new OKR experience view as "Committed," the "Planned Value" of this objective does not reflect in the charts.

      However, if the objective is created from the legacy experience, as "Critical Path" (same type as Commiited in the new experience), the planned value of the objective is reflected in the charts.

      This is important for the customer to show the accurate data to stakeholders in the Progress by Objective report.

      Steps to Reproduce

      1. Select a program and a PI > Reports > Progress By Objective report
      2. For that particular PI, note the Planned Value in the 3 charts at the top of the report. (i.e., 40)
      3. From the new OKR experience, start to add a new objective. (Program or Team etc.)
      4. Select objective type as "Committed" and pick a Planned Value from the drop-down (i.e, 10)
      5. Go back to the Progress By Objective Report and check the planned value in the charts
      6. Confirm that the new Objective's planned value does not reflect in the chats (expected to see planned value as 50)
      7. However, the "Planned value" shows the correct number in the table below of the report
      8. Follow the same steps in the legacy experience, and confirm that the planned value is reflected in the charts

      Expected Results

      The Objective planned value to reflected in the charts

      Actual Results

      The objective planned value does not reflect in the charts

      Workaround

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

            Assignee:
            Don Fuller
            Reporter:
            Can Mutlugeldi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: