Closed cdokolas closed 7 years ago
hi, i am sorry, but please provide more informations, e.g. did you book some time from this timelog before? In the end, try deleting the booking and create a new booking, sometimes this helps.
I thought I made it clear on the issue title that I booked the full time all at once. I will try what you suggest, but I believe there is a bug none the less (i.e. I may use the workaround, but the issue should stay open).
Anything else you might need to reproduce the bug?
well, anything helps ;) The point is, we use this plugin in production everyday and it works as expected. So i need every information, you think is different from a default system. Maybe other plugins, configuration, user acces roles and rights for this specific time log, etc.
Oops! Hadn't seen your reply. Here you go with some more info:
From the Redmine information page:
Environment:
Redmine version 2.6.5.stable
Ruby version 2.0.0-p353 (2013-11-22) [x86_64-linux]
Rails version 3.2.21
Environment production
Database adapter Mysql2
SCM:
Subversion 1.8.8
Mercurial 2.8.2
Git 2.2.0
Filesystem
Redmine plugins:
clipboard_image_paste 1.10
collapsed_journals 0.0.3
redmine_better_gantt_chart 0.9.0
redmine_favourite_projects 0.7
redmine_slack 0.1
redmine_time_tracker 0.9.20
Also:
Hello,
I do have the same issue. After booking time to different tickets, a time log remains with 00:00h. A deletion of this time log is not possible.
Please find a screenshot of the problem attached. The version of the Timetracker Plugin I use is 0.10.5, the Redmine version is 3.1.2.stable.
Hi there, the problem is that you have a missing minute from 04:28 to 04:29, but the time log doesn't display this right and says it's 0:00. Change it, so that the start time of one is the stop time of the other. Then the timelog should be hidden. Greetings, jume
Thanks, that was the problem! :-)
Any idea why the time isn't displayed correctly? Maybe it is some kind of rounding issue.
yeah, probably a rounding bug, will be fixed with the new release anytime soon
whoops, forgot @cdokolas issue. But i guess that is kinda the same as the other one.
These kind of problems are fixed with the new version.
I had a time log of 1:05 which I booked by assigning the issue number and picking an activity, and now it is still visible with 00:00 bookable time.
Log details: