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

Daily Standup | Meeting Summary | Planned vs. Earned Velocity report displays incorrect info

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      1. Planned vs. Earned Velocity report displays incorrect Planned velocity for sprint value under Daily Standup > Meeting Summary

      Note: The issue is same as https://jira.atlassian.com/browse/JIRAALIGN-3992 but not from reports but from Daily Standup > Meeting Summary

      Steps to Reproduce

      Confirm that the prereqs are met mentioned under - https://help.jiraalign.com/hc/en-us/articles/115004530827-Planned-vs-earned-velocity and https://help.jiraalign.com/hc/en-us/articles/360002216494-Points-planned-vs-points-accepted

      For issue 1:

      • Go to Daily Stand-up > Planned vs. Earned Velocity report
      • Select a sprint 
      • Planned velocity for sprint is not matching actual planned story point total for this sprint

      Screenshots:

      • On the Daily Standup - Planned vs Earned graph, especially for PI4.2 iteration we see that the planned effort is 0 which is not true as per the above screenshot. All stories have value for LOE planned in the iteration

      Expected Results

      • Daily standup meeting summary graph should display actual value of planned vs earned effort..

      Actual Results

      • Daily standup meeting summary graph should display actual value of planned vs earned effort.

      Workaround

      None

        1. Reports_PlannedVSEarned.png
          Reports_PlannedVSEarned.png
          956 kB
        2. Story view_2023-02-24T12_39_03.972Z.png
          Story view_2023-02-24T12_39_03.972Z.png
          815 kB
        3. tw1.jpg
          tw1.jpg
          36 kB

            9ca9aa5ad14e Sam Tsubota
            1b55d4e67612 Manideep Neeli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: