Committed Story Points changes on a closed Sprint.

XMLWordPrintable

    • Type: Bug
    • Resolution: Not a bug
    • Priority: Low
    • None
    • Affects Version/s: 9.4.2
    • Component/s: Reports, Sprint
    • None
    • 9.04
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 Aug 2024

      Hi everyone,

      This issue has been reviewed by the Jira Data Center Development team. As a result of our investigation, we found out that described behaviour is expected.
      Reports in Jira by design always present current state of the database. Jira is not persisting snapshots of past states and reports are not static. They are recalculated every time user access the page based on the current state of the Jira. Hence we are closing the bug.

      We realize our decision may be disappointing, and we will continue to monitor this issue for further updates. Please continue to share your thoughts in the comments. Thank you for your patience and understanding.

      Best regards,
      Daniel Dudziak
      Principal Software Engineer

      Show
      Atlassian Update – 06 Aug 2024 Hi everyone, This issue has been reviewed by the Jira Data Center Development team. As a result of our investigation, we found out that described behaviour is expected. Reports in Jira by design always present current state of the database. Jira is not persisting snapshots of past states and reports are not static. They are recalculated every time user access the page based on the current state of the Jira. Hence we are closing the bug. We realize our decision may be disappointing, and we will continue to monitor this issue for further updates. Please continue to share your thoughts in the comments. Thank you for your patience and understanding. Best regards, Daniel Dudziak Principal Software Engineer

      Issue Summary

      • Removing issues from a Sprint and changing their Estimates would cause the Velocity Chart Report to change the Original Committed Story points on the Closed Sprint.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Started 'Sample Sprint 3' with 18 Story Points
      2. Move two issues with 2 Story Points each to 'Sample Sprint 4' (SCRUM-1 and SCRUM-2).
      3. Completed the 'Sample Sprint 3'.
      4. The Velocity Chart Report shows the "original" Committed Points = 18 for 'Sample Sprint 3'
      5. Proceeded to change the Estimate Story Points for both SCRUM-1 and SCRUM-2 from 2 to 4 Story Points.
      6. Re-checking the Velocity Chart Report and noticed that it now shows Committed Points = 14. It seems that the report changed for the closed print and removed 4 points, from those issues that were removed and had Story Points changed.

      Expected Results

      • The velocity chart would keep the original data.

      Actual Results

      • The velocity chart changes the Committed Story Points for an already Closed Sprint.

      Workaround

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

        1. SampleSprint4-2.png
          SampleSprint4-2.png
          111 kB
        2. SampleSprint3Complete-2.png
          SampleSprint3Complete-2.png
          183 kB
        3. SampleSprint3Complete.png
          SampleSprint3Complete.png
          199 kB
        4. SampleSprint4.png
          SampleSprint4.png
          345 kB
        5. SampleSprint3.png
          SampleSprint3.png
          291 kB

            Assignee:
            Unassigned
            Reporter:
            Diogo Wunsch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: