Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-15793

Sprint burndown chart does not include work logged or time spent

    XMLWordPrintable

Details

    Description

      When work is logged against an issue via a transition screen, the RTE change isn't recorded in the Sprint burndown report/table.
      Example of issue ABC-2 that's been added to sprint and has work logged against it in the same minute:

      Expected result in burndown report:

      Actual result:

      Note the missing row for "Work logged" and the values in the "Time Spent" columns.

      Steps to reproduce:

      1. Make a scrum board.
      2. Configure the board to have time tracking. Board > Configure > Estimation and pick "Remaining Estimate and Time Spent":
      3. Add the "Log Work" field to the board's issue screen. You can do this from the edit dialog of an issue > Configure fields > Where is my field and adding "Log Work" to the screen.
      4. Go back to the board and create a sprint.
      5. Add an issue to the sprint and give it a remaining time estimate (60m in my screenshot).
      6. Do this in the same minute of the clock: start the sprint and log work for the issue (10m in my screenshot).
      7. Check the Burndown chart for this sprint. You should see that the "log work" entry is missing from the report.
        I suspect this is caused somewhere in BurndownChangeUtil.java when we get the changes per issue. If that's the case, make sure all the charts/reports involved are also checked.

      Context: https://support.atlassian.com/browse/JST-217975.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nso@atlassian.com Nara So
              Votes:
              4 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: