Is this a…:
Standard bug Steps to reproduce this issue:
When I want to attach a closure to an event, I have a huge list that includes all past events, and it’s not easy to find the good one.
It should be filtered to match the closing date.
The same goes for the waze events page
Environment where the bug occurs…:
All environments Permalink:
Browser name and version:
Chrome 137.0.7151.120 Are you using scripts? Please detail which ones.:
No
Thank you for submitting this bug report. Could you please record a video to show how you’re searching for the event? I tried to reproduce the issue on my side using the location from your permalink but didn’t see the same long list of events.
The size of the list doesn’t really matter it’s linked to the bug, what’s missing, and what’s important, is that the date doesn’t act as a filter, we should only see proposed events that fall on that date.
This is how things worked before the changes.
If I want to modify/duplicate an event, I don’t do it in this tab, I do it in the events tab.
Regards
edit: Another thing I’ve just noticed is that we can now add closures to a past event, before we couldn’t, there was an error that appeared.
Hi,
It seems that I get now a whole list of events in the drop down list when I want to link a closure to an event.
Possible events, including the locationless:
I should note this is adding significantly more work to placing RTCs and creating MTEs. Whether it be sifting through the giant list or differentiating between an expired MTE or the present one.
Many large scale events occur annually and differentiating between the active event for this year or the one from last year can only be done by trial and error.
Experiencing the same issue. Please revert to how MTEs were handled before. Usually the RTC list of MTE’s only populated current MTEs and only MTEs that were in the vicinity of where you’re editing/adding RTCs. I’m now seeing a whole super long list of all events in my state past and present. Whatever was changed is NOT useful and is, in fact, more time consuming to the workflow of adding RTCs tied to MTEs.
Could you please recheck the behaviour in the WME beta?
Just a heads-up — you might still see past events when creating closures. This happens because the backend includes all events linked to closures in the area, even if they’ve already ended. You may need them in order to duplicate past closures in the same area.
If you feel this behavior is confusing or could be improved, feel free to open a suggestion explaining how a change in the logic might be helpful.