-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Took from slack
If I have a time entry that starts at 11:00:00 and I go to create one that starts at 09:00:00 and ends at 11:00:00 it is rejected saying my new entry "overlaps" another entry. This seems like cruel and unusual punishment to make the user input 10:59:59. For those of us who are heavy multitaskers it's not exactly clear to me that overlap should be prohibited anyway. But I digress. I think one second of overlap.... Or perhaps a "fix" button that will snap to the value automatically.
The easiest way to deal with this problem would be substracting one second from the end_date or adding a second to the start_date if a conflict is found.
If after applying these changes, we still have conflicts, we should display the same error message.