Hi Everyone 
We hope you’re all doing great.
We’ve just released a new version of WME v2.325 
Below you can find a summary of the release.
Community Suggestions:
1. Online Editors - make visible by default upon the first login: We are deploying changes so that upon a user’s first login to the Waze Map Editor (WME), their online status will be automatically set to “Visible.”
- To communicate this change, a one-time tip/pop-up message will be displayed during the first session confirming their online status.
- After the user dismisses this initial tip, it will not reappear.
- If an editor hasn’t intentionally changed their status to invisible, they will now be visible.
- Users retain the ability to manually change their visibility status to “Hidden” at any time via WME settings.
- Community suggestion: “In WME: Force L1 & L2 editors to be “visible”
- Thank you @kodi75 for submitting it and everyone else for upvoting!
2. Venue Matching External Provider Flow: In this version, we are adding an improvement to the flow where you link venues with external providers. From now on, when you select an item from the dropdown, the venue will be linked automatically without needing to click “Add” or “Cancel.”
- Thank you @YanisKyr for raising this suggestion in the “Let’s Empower Our New Editors with Targeted MapRaids!” thread (access is limited to Community Coordinators and Global Champs).
New features/enhancements:
1. Issue Tracker - pagination API revamp: We are working on internal infrastructure updates and one of the stages is to make the Issue Tracker faster when handling and displaying large lists of issues under the Solve tab.
In the previous approach, the backend (BE) would send us a batch of 500 items for the list of issues in the Issue Tracker. We displayed all 500 items, and when users scrolled through all of them, a spinner would appear, and a new batch of items would be fetched from the BE.
Now, we are changing the logic, and the load limit will be 240 items (8 pages), allowing for a faster load of such issues. After scrolling through them, you will see the spinner appear again. At the same time, you will see the precise number of found items in both the tabs and the pagination.
2. Issue Tracker UI: with this release we introduce a change to the URs icons. It is related to a future pre-beta testing process, mentioned in this Heads-up post.
*We have already received some valuable feedback during the beta testing with regards to the sizing of the new UR icons and have passed it to the team for further consideration.
3. Performance improvement: We’ve changed the way the WME handles map markers (icons for permanent hazards, house numbers, closures etc.). This ensures better memory usage when related layers are turned on, leading to a smoother user experience, especially over long sessions.
We’d like to ask you to pay attention to these changes and share your feedback if you notice any improvements or issues.
4. SDK improvements: please refer to the change log to check the SDK additions.
Bug fixes:
We released 4 bug fixes:
1. Suggest an Edit on Segments:
-
Resolved the issue where the suggest an edit mode prevented level 4-6 editor from directly saving new segments in their area.
-
Handled the case that users were unable to split a segment with a new segment (change was un-done)
2. Place update requests: addressed the case where the house number wasn’t displayed in Place Update Request.
3. Closures: fixed the issue where the “Provided by” field was automatically associated with the “French Community,” even when “None” was selected as the source.
- This issue has been raised by the French Community.
Known issues:
1. UR Icons:
- Bubble icon with 3 dots appears near the UR’s pin only after adding the first comment and disappears after refreshing the map >> currently in the works.
- The “Not Identified / Closed” Update Request icons display with incorrect and inconsistent sizing on the map.
You can read more here.
We look forward to receiving your feedback! 
Thank you and regards,
Olesya
