Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-9885

Sprint Health Gadget appears to double count scope change

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.3.13.0
    • Component/s: None
    • Labels:

      Description

      This is an excerpt of the logging output from the Sprint Health Gadget

       Calculating sprint completion [sprint duration=9.999828125, time worked since sprint start=0.004975567129629629]
       Calculating scope changes for sprint[id=48, name=Sprint 18, startDate=01-10-13 01:26 +1000, endDate=15-10-13 02:26 +1100]
       Burndown change[issueKey=BS-4, time=30-09-13 11:27 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-5, time=30-09-13 11:27 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-6, time=30-09-13 11:27 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-7, time=30-09-13 11:27 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-4, time=30-09-13 11:27 +1000, added=null, newValue=1.0, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-5, time=30-09-13 11:27 +1000, added=null, newValue=2.0, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-6, time=30-09-13 11:27 +1000, added=null, newValue=3.0, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-7, time=30-09-13 11:27 +1000, added=null, newValue=4.0, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-12, time=30-09-13 11:48 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-14, time=30-09-13 11:50 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-14, time=01-10-13 01:17 +1000, added=null, newValue=8.0, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-12, time=01-10-13 01:17 +1000, added=null, newValue=4.0, oldValue=null]
       Intermediate estimate at sprint start [0.0] and after sprint start [0.0]
       Burndown change[issueKey=BS-6, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue to sprint before start
       Intermediate estimate at sprint start [3.0] and after sprint start [3.0]
       Burndown change[issueKey=BS-7, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue to sprint before start
       Intermediate estimate at sprint start [7.0] and after sprint start [7.0]
       Burndown change[issueKey=BS-14, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue to sprint before start
       Intermediate estimate at sprint start [15.0] and after sprint start [15.0]
       Burndown change[issueKey=BS-4, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue to sprint before start
       Intermediate estimate at sprint start [16.0] and after sprint start [16.0]
       Burndown change[issueKey=BS-5, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue to sprint before start
       Intermediate estimate at sprint start [18.0] and after sprint start [18.0]
       Burndown change[issueKey=BS-12, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue to sprint before start
       Intermediate estimate at sprint start [22.0] and after sprint start [22.0]
       Burndown change[issueKey=BS-15, time=01-10-13 01:26 +1000, added=null, newValue=null, oldValue=null]
       Intermediate estimate at sprint start [22.0] and after sprint start [22.0]
       Burndown change[issueKey=BS-15, time=01-10-13 01:26 +1000, added=null, newValue=2.0, oldValue=null]
        -> Estimate set for the first time after sprint start
       Intermediate estimate at sprint start [22.0] and after sprint start [24.0]
       Burndown change[issueKey=BS-15, time=01-10-13 01:26 +1000, added=true, newValue=null, oldValue=null]
        -> Added issue after sprint started
       Intermediate estimate at sprint start [22.0] and after sprint start [26.0]
       Estimate at sprint start [22.0] and after sprint start [26.0]
      

      Basically, I had 22 points in the sprint when the sprint started, and then I added one story with 2 points. The scope change amount was shown as 18%, when it should be 9%. The logs confirm that the code is double counting this added issue.

      To reproduce the problem, the issue that is added must have been created after sprint start, and it must have had its estimate applied before it was added to the sprint.

        Attachments

        1. 404.php
          447 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              mtokar Michael Tokar
              Votes:
              9 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: