Reported when the report for time zones needing to be in event was producted
Excerpt from slack
Following a recent update to the screen for adding shifts, when opening a shift Uber attempts to convert times from the event time zone (presumably America/New_York) to the browser's locale time zone, and when saving the job will attempt to convert the time from the browser's locale time zone to event time zone. Uber also forbids at-event shifts outside of a specific window of dates/times.
My browser's locale is UTC. (short explanation: Librewolf)
The upshot is that attempting to edit a shift at the end of the event will cause Uber to null out the start time for the shift (because it translates the start time five hours later to an invalid time), and attempting to save the shift will delete it instead. I also cannot replace the shift because in order to work within the system I would have to make it start at 19:15 Sunday (which Uber will not let me do with an at-event shift).
Please remove the time zone translation step. I don't think there's a use case for displaying any time zone outside the event's time zone. (edited)
Event time zone fix is in PR that should merge shortly (so likely fixed for future readers).
As of the moment cannot reproduce deleting a shift. Logging here for further investigation. (this may be because time bounds are now fixed?)
Reported when the report for time zones needing to be in event was producted
Excerpt from slack
Following a recent update to the screen for adding shifts, when opening a shift Uber attempts to convert times from the event time zone (presumably America/New_York) to the browser's locale time zone, and when saving the job will attempt to convert the time from the browser's locale time zone to event time zone. Uber also forbids at-event shifts outside of a specific window of dates/times.
My browser's locale is UTC. (short explanation: Librewolf)
The upshot is that attempting to edit a shift at the end of the event will cause Uber to null out the start time for the shift (because it translates the start time five hours later to an invalid time), and attempting to save the shift will delete it instead. I also cannot replace the shift because in order to work within the system I would have to make it start at 19:15 Sunday (which Uber will not let me do with an at-event shift).
Please remove the time zone translation step. I don't think there's a use case for displaying any time zone outside the event's time zone. (edited)
Event time zone fix is in PR that should merge shortly (so likely fixed for future readers).
As of the moment cannot reproduce deleting a shift. Logging here for further investigation. (this may be because time bounds are now fixed?)