Suggestion 1 and 2 are connected to the same segment
Suggestion 1 gets approved
Existing segment gets split and two new IDs are generated
Suggestion 2 becomes “orphan”
I’ve recorded two examples:
Environment where the bug occurs: ROW Permalink: n/a Browser name and version: Chrome, Firefox, Edge, Safari (all behave the same) Are you using scripts? Please detail which ones.: No scripts.
Thank you for your input.
The behavior where one of the suggestions disappears after the original segment it was meant to be connected to is split is WAD:
WAD as in Waze-didn’t-think-About-it-during-Design I guess
That’s quite disappointing to hear.. Editors invest their own time to submit map suggestions, and we’re just going to shrug at that? That’s rather confusing and frankly quite discouraging too!
This is just technically challenging at present. I am open to your suggestions, however, and can bring it up to the team. I shared the current status as we have it today; “WAD” is never intended to shrug at things.
Sure, thank you. Here is one idea.. keep the Suggestion in place in WME, and leave the affected segment end(s) disconnected
By lack of communication, the current workflow is ignoring the suggestion. The least we could do is inform the user that their Suggestion has been eliminated/affected/rejected.