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

Epic Planning Link: Incorrect Burn Down Calculation For Story Points

    XMLWordPrintable

Details

    • 2
    • Severity 3 - Minor
    • Sticky Bandits - WT2
    • No

    Description

      Issue Summary

      We have discovered that there is an issue with the Epic burn down by story points on the Epic planning link (epic slide out).  The burndown calculations is way off. You'll notice a big diference when you compare this to the Epic burndown by story via the PIP report (drill-down view by Epic).

      Steps to Reproduce

      1. Step 1 - Select an Epic
      2. Step 2 - Ensure that there is multiple PIs associated with children work items tied to the PIs
      3. Step 3 - Ensure that stories are associated to this Epic 
      4. Step 4 - Ensure that some stories are completed (Accepted)
      5. Step 5 - Run the Planning View and select burndown by story (Select PI)
      6. Step 6 - Compare those results by selecting the same PI and associated program on the Epic drill down report via the PIP report

      Expected Results

      Points remaining = SUM of story LOE parented to epic and planned for selected PI in the planning modal - SUM of LOE of stories accepted parented to epic and planned for selected PI in the planning modal

      • do not include misaligned sprint stories (if PI selected is PI-1, and the story has PI-1 but sprint in PI-2, then it should not show here)

        Actual Results

      Story point totals aren't accurate

      Workaround

      Users must view the PIP report vs the Epic planning link to get the accurate Epic burn down metrics

      Attachments

        Issue Links

          Activity

            People

              rvozniak@atlassian.com Roman Vozniak
              ddortch@atlassian.com Darryl Dortch (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync