hicknhack-software / redmine_time_tracker

A time tracker plugin for Redmine
Other
106 stars 32 forks source link

Cannot remove last time log #104

Closed rbugajewski closed 7 years ago

rbugajewski commented 11 years ago

I have a time log that I cannot remove. When I right click on the entry and select “Delete” I get the following error message:

Updating time log would result in negative bookable time. Not allowed!

This is the last not booked time log entry. Shouldn’t I be allowed to just delete it? Could it be that there’s somewhere a comparison to < 0 instead of <= 0?

jume-dev commented 11 years ago

I am not exactly sure about this issue, but could it be, you already booked some time from this time log? I dont think you can book only a split time and delete the rest.

rbugajewski commented 11 years ago

I’m not exactly sure what happened, but I was confused by the user interface. I solved this issue by changing the logged time from over 8 hours to 2 hours. Then I removed the entry completely.

I’m sure that there was some overlapping booked & logged time and it could be that I indeed already booked some time from that entry.

  1. Why shouldn’t it be possible to book only some time from a log and delete the rest?
  2. Why did the interface let me delete it after I changed the logged time? (I booked about 40 minutes, the interface didn’t let me change the logged time to less than that; after I changed it to 2 hours I could delete it nonetheless)
jume-dev commented 11 years ago

good questions, will implement something to deal with such cases

h0lg commented 10 years ago

+1 this regularly happens to me too. Those partly booked time logs pile up at the top of my overview right now because I'm unable to delete them.

cforce commented 10 years ago

+1

jume-dev commented 10 years ago

just a notice for me (or anyone else who wants to implement something to fix the issue): The wished behavior is actually implemented but it only works with linear splitting of timelogs. So, we should discuss about #168 and then implement a clean, working solution

jume-dev commented 7 years ago

This is fixed in the new version by forcing a 1 to 1 connection between logs and bookings.