When a warning such as a segment is part of a junction box a is displayed in the left panel the warning does not scroll away in the current WME beta. The previous behavior used to allow this warning to be scrolled away. The new behavior is for this warning to stay persistent. The new behavior makes it so there is very limited space to see the segment properties. This is especially problematic when trying to edit things like lanes where it is necessary to see what lanes are being assigned to each road.

The suggestion is to revert the current behavior to the previous behavior, let the warning be scrolled away.

Here is a video of the previous behavior- https://drive.google.com/file/d/1z-FAgdlmry3PcTV48Z-dzecBP4l_P3OR/view?usp=sharing

Here is a video of the new behavior- https://drive.google.com/file/d/1iOcYFE_vhNCjJuToO8RrgTm6HMWqW-RN/view?usp=sharing

Given that the appearance of SLURs has now calmed down I would like to make a proposal to move SLURs from beta to production editor.

There are, however, two questions to everyone in ROW:
1) can you reports SLs from app? New SLURs pop up from time to time, but I haven't been able to make one myself;
2) would you like to bring all previous SLURs to prod or have a reset and make a fresh start? My vote goes to "bring everything to prod", because the current amount and appearance of new ones is manageable.

By: matsalka
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=274475

It would be very nice if we could filter the feed by notification types (more or less like URO+ does, but without having to reload the feed several times to find the ones you selected).

Options suggested:

Notifications (checkboxes):
- PURs (and subtypes);
- URs (and subtypes);
- PMs.

Areas:
- State XX (particularly useful for SMs and CMs);
- Areas driven [last XX days];
- Country (useful for CMs);
- All editable areas.

Those above are what I miss the most. But, since we're at it, some extra suggestions would be:

Listing reason:
- Reported by you;
- New comments on an issue you follow;
- An issue you follow;
- Around a favorite place.

Sort by:
- Time open (asc/desc);
- Number of comments (for URs) (asc/desc);
- Distance (of current shown position).

Some other thoughts about this suggestion are welcome! ;)

By: GuibaBR
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=198461

Hi,
a few month ago Irad told to make suggestions about SLUR, I took my time but here it is :

In the beginning, we had a SLUR for every request, and there were way too much of them because sometimes there is a lag in showing the new speed limit so people were reporting speed limit that were already good, and also because speed limit were not visible in the client until you exceeds the limit.

The idea of grouping them making cluster was implemented (against our will), and according to Merav last time I spoke with her about it, it was a "total failure" with groups of different update requests in various languages where we miss the localization since they are grouped on one request at a random place of the segment : "Speed limit: 90 km/h,Limite de vitesse : 70 km/h" And it is a nice one, sometimes you have 5 different speed reported".

When you answer you don't know if nobody receive the response, or if everybody is getting it or maybe one of the reporter.

What I suggest since the beginning :

Do not group requests in a cluster
Ignore update requests suggesting the speed that is already set on the segment (if someone reports 90km/h on a segment but it is already 90, just close the SLUR without showing it in WME.
Do not allow user to submit SLUR in the wrong unit. If I am in France people should never submit a speed in miles/h.

by kpouer
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=284047