Open johnclary opened 3 years ago
I have this mocked up in the 31 DEC test env.
We need to do this after 4pm because it's going to slow down the data tracker while historical values are calculating
work_order_signals_time_logs
object({leave_worksite}-{arrive_worksite})/3600000
work_orders_signals
objectAlso, we'll need to trigger a batch update on both objects to make sure that we backfill these fields for historical work orders.
@dianamartin earmarking this for you but we can assign to someone else. let's discuss in grooming. cc @amenity
ah—realizing now we need to think about how best to calculate this. there are actually four timestamps on the timelog:
and they're not all consistently used. we've got to talk to Jen/Brian VDW/Billy about this.
@johnclary - do you want me to set up a meeting or just add to #5373?
As a manager, I need to be able to calculate the total # of hours worked on a work order so that I can estimate total costs and process reimbursements accordingly.
The Data Tracker should automatically calculate the total hours worked on a given work order based on the sum of the time logs associated with it.
This request came from Peggy/Jen as we struggled to report hours worked during the winter storm to FEMA.