Begin of the insertion**As an** employee

**IEnd of the insertion Begin of the deletion As an employee, IEnd of the deletion want Begin of the insertionto**End of the insertion Begin of the deletion toEnd of the deletion enter a start and end time when creating time Begin of the insertionentries

**so that**End of the insertion Begin of the deletion entries, so thatEnd of the deletion my company can deliver detailed Begin of the insertiontime sheetsEnd of the insertion Begin of the deletion timesheetsEnd of the deletion to my customers

### Use case

Some customers require detailed Begin of the insertiontime sheetsEnd of the insertion Begin of the deletion timesheetsEnd of the deletion when I bill them. They do not only want to see how long I have been working on a task, but also when I started and ended. Start and end-time can be very important for interventions outside normal business hours, because they are sometimes billed at a higher rate.

### Current Workaround

I defined to string custom fields with a regex, so that it is possible to enter a start and end time. That works fine, although there is no logic and no validation behind Begin of the insertionit.End of the insertion Begin of the deletion it. End of the deletion

And in the standard cost report they are not visible.

### Proposal

* Something like this (screen shot from my own client, so that's why it's not familiar): Begin of the insertion


<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/18856/content" alt="">End of the insertion

Begin of the deletion 

End of the deletion * in case creating time entries that pass over midnight is important, it could look like outlook appointments: Begin of the insertion


<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/18857/content" alt="">End of the insertion

Begin of the deletion 

End of the deletion * Whether Start/End time is required, should be configurable, preferably on system and project level Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion ### Implementation

* store start and end date-time in the database (easy for finding double-bookings for a single employee) or store start date-time and duration (easier implementation when start and end time is not used and for migration of existing data)