Details
-
Bug
-
Resolution: Timed out
-
Low
-
9
-
Severity 3 - Minor
-
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:
- Make a scrum board.
- Configure the board to have time tracking. Board > Configure > Estimation and pick "Remaining Estimate and Time Spent":
- 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.
- Go back to the board and create a sprint.
- Add an issue to the sprint and give it a remaining time estimate (60m in my screenshot).
- Do this in the same minute of the clock: start the sprint and log work for the issue (10m in my screenshot).
- 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.
Attachments
Issue Links
- is related to
-
JSWCLOUD-16095 Sprint burndown does not include "work logged"/"time spent" if date started is altered manually to be earlier than issue creation date
- Closed