Tempo Ideas

The daily worklog time summary must calculate the effective working time of an employee and must not simply add up all worklog durations when worklogs overlap. The system needs to clearly distinguish between working time reporting and project timesheet reporting, because both use cases have different business semantics. For working time, overlapping intervals must be counted only once, since an employee cannot work twice during the same time period. For project timesheets, however, the individual project bookings must remain unchanged, because they represent time allocation to Jira projects or issues.

Example: Meeting #1 is booked for Jira Project A from 13:00 to 15:00, resulting in 2 hours. Meeting #2 is booked for Jira Project B from 14:00 to 18:00, resulting in 4 hours. From a project timesheet perspective, both bookings are correct and must be shown independently: Project A = 2 hours and Project B = 4 hours. However, from a daily working time perspective, the employee only worked within the time range 13:00 to 18:00, so the effective working time is 5 hours, not 6 hours. The overlapping period from 14:00 to 15:00 must not be counted twice.

The proposed solution is to apply different calculation logic depending on the reporting context. In working time summaries, employee working hour reports, overtime calculations, or payroll-relevant views, the system should merge overlapping worklog intervals and calculate only the actual covered time span. In project timesheets, project reporting, cost allocation, and Jira project time spent views, the system should continue to count each worklog independently. In addition, the system should provide transparency by flagging overlapping worklogs or offering an admin report that shows which employees, dates, and time ranges contain overlaps. This is required because employers currently cannot efficiently identify these overlaps, while employees may incorrectly assume that the inflated daily total represents valid overtime and may expect additional payment. This creates operational, financial, and compliance risk and makes the current behavior unacceptable for reliable working hours logging.