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

"Commited Work" items in the Iteration Metric and Iteration Coaching pages does not match what is in Jira

    XMLWordPrintable

Details

    • 2
    • Severity 2 - Major
    • A-Team - Usher8

    Description

      Issue Summary

      The "Iteration Metric" and "Iteration Coaching" pages are showing the same incorrect data. "Committed Work" shows more "User Stories" than expected by the user in comparison with the "Sprint Report" from Jira.

      Steps to Reproduce

      Example scenario from a Jira Align User

      • Navigate to the Jira Align Iteration metric note that there are 28 stories planned and 5 completed for that Sprint
      • Navigate to the Jira Align Iteration Coaching and also note that there are 28 stories planned and 5 completed for the Sprint
      • Finally, navigate to Jira and note that there were only 8 stories planned and 5 completed. That is what really happened in the Sprint and Jira is the source of truth in this case.

      Expected Results

      The Iteration Metric and Iteration Coaching reports should line up with what is reported in Jira for the planned and completed stories.
      Stories are count as Committed only if they are assigned to a sprint before it's start date in Jira Align. Planned and Accepted are stories are counted when stories are assigned to sprint regardless of when they were assigned.

      Actual Results

      See above. The Jira Align reports are both incorrect with regard to the number of planned stories.

      Workaround

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

      Attachments

        Issue Links

          Activity

            People

              tdavenport@atlassian.com Tony D.
              kbaxley Kent Baxley
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync