-
Bug
-
Resolution: Obsolete
-
Low
-
6
-
Severity 3 - Minor
-
Summary
If the user log works in an issue and manually change the date of the Logged Work "Date Started" to sometime before the issue creation date, the Burndown chart won't take this Log Work into account.
Environment
JIRA Software Cloud
Steps to Reproduce
- Create a board with a Sprint and a few issues;
- Put the board estimation to be "Original Time Estimate" and enable "Time Tracking";
- Start the Sprint, edit the start date of the sprint to an earlier time to test it easily
- Log Work in an issue setting the day of this logged work to be before the issue creation, but after the sprint start date
- Select the report of Burndown with "Remaining Time Estimate" as the reference, so the "Time Spent" progress line appears
Expected Results
JIRA Software burndown chart should, at least, show the logged work entry for the day it was committed.
It would be better if the burndown chart could also take into account the actual Date Started.
Actual Results
The entry is not processed by the Burndown chart
- The time spent line does not indicate that time logged
- The summary below also does not capture this time logged event
Workaround
Manually edit the start date to be after the issue creation date
- is blocked by
-
JSWCLOUD-16949 Burndown chart shows logged hours on the incorrect date
- Closed
- relates to
-
JSWCLOUD-15793 Sprint burndown chart does not include work logged or time spent
- Closed