Is this a…:
Standard bug
Steps to reproduce this issue:
When using the “Import closure from map problem” feature, the dates and times of the closure are in UTC time instead of reflecting the time listed on the MP. For example a location where local time is UTC+10 means the imported dates and times will be 10 hours behind the MP’s closure times. This is occurring in both beta and prod.
I have attached 2 screenshots:
- One from Queensland, Australia where local time is UTC+10 so times are imported as 10 hours beforehand
- One from New South Whales where local time is currently UTC+11 so times are imported as 11 hours beforehand
Steps to reproduce:
- Find a closure MP in timezone other than UTC+0 (e.g. https://waze.com/en-AU/editor?env=row&lat=-22.86747&lon=139.85633&zoomLevel=18&mapProblem=3%2F8685969 )
- Left click to select the MP
- Left click on a segment to select it
- Click on the closures tab in the side panel
- Click on “Import closure from map problem”
- Notice the dates and times autofilled for the closure are different to the MP
Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/en-AU/editor?env=row&lat=-22.86747&lon=139.85633&zoomLevel=18&mapProblem=3%2F8685969
Browser name and version:
Google Chrome Version 142.0.7444.60 (Official Build) (arm64)
Are you using scripts? Please detail which ones.:
No
