-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: Space - Reports
-
5
-
Severity 3 - Minor
Summary
When logging work in the New Issue View, the Start Date field is automatically set to (local time - work logged). In the issue history, the logged work action is displayed as (local time - work logged) causing it to no be displayed in the Burndown Chart.
Steps to reproduce
- An issue is worked and then added to the Active Sprint;
- The work is logged in the issue;
- If using the new issue view, the logged work won't reflect in the Burndown Chart;
- On the old issue view, it will correctly reflect.
New issue view: Screen Recording 2020-07-06 at 11.13 AM.mp4
Old Issue view: Screen Recording 2020-07-06 at 11.14 AM.mp4
In this example, the work was logged twice, one in the new issue view and one in the old. We can see that only the second is logged.
Expected Results
The logged work is displayed in the Burndown Chart.
Actual Results
Logged work in the new issue view does not reflect in the Burndown Chart.
Workaround
Log work in the old issue view.
- relates to
-
JRACLOUD-74752 When logging time with Time Tracking, the work log entry is showing a past entry rather than current.
-
- Closed
-
-
BENTO-7148 Loading...
- mentioned in
-
Page Loading...