Date inconsistency between timetracking and booking

hicknhack-software / redmine_time_tracker

A time tracker plugin for Redmine

Other

106 stars 32 forks source link

Date inconsistency between timetracking and booking #168

Closed jume-dev closed 7 years ago

jume-dev commented 10 years ago

I have a Tracking with 1h time and i book 30min of this to a project. Now i change the date of the timetracking to another date, but the date of the bookings stays the same. While i understand the logic behind this, it is kinda inconsistent, because the bookings is still linked with the now changed timetracking.

Maybe we should discuss about a change here. It would be possible to create two different time trackings each time only a portion of a tracking is booked

jume-dev commented 10 years ago

We discussed this and found following solution:

time bookings should be stripped of the date attribute and instead use the date from the time tracking
time bookings should be stripped of the start and end time in hard values, instead use offsets based on the time tracking start time

rbugajewski commented 10 years ago

I still don’t understand the complexity behind the whole tracking / booking system. It would kind of make sense when there would be one person who only tracks time and then another person (like a project manager) would take this time and book all time trackings. My point is that I don’t understand why the current interface doesn’t give me the option to say: “I worked yesterday from 09am–05pm and I want to book this right now.”

What I’m doing now in such a case is that I start the time tracker, change the date to yesterday, stop the time tracker, book the appropriate hours, go into the database and delete the remaining tracked—but not booked—time.

Would your solution also cover this use case?

arBmind commented 10 years ago

Stripping the absolute data, is not an option, if we want to improve the interoperability between time_tracker_plugin and redmine native time bookings. Also the calculations require more effort for every display. Instead the date and time of all bookings should be corrected, when a tracking is changed or easier changing trackings should be disallowed as soon as a booking for it exists.

jume-dev commented 7 years ago

For the new version we opted for an 1 to 1 connecetion between time logs and time bookings. Also the bookings get updated whenever the date of the time log changes.

The offset approach didn't work as needed and created more problems as it solved.

About the time "i worked yesterday and want to book" stuff, that's kinda using redmines own time tracking. The plugin itself is not capable of this yet. But for the new version we are probably gonna implement this.