[Mevaseret Zion] Can't reject an edit suggestion

Try to reject this edit suggestion. It results in no permissions for updating edit proposal.

Stats for nerds

Response from backend:

{
  "errorLevel": "ERROR",
  "errorList": [
    {
      "code": 101,
      "details": "No permissions for updating edit proposal",
      "geometry": {
        "type": "Point",
        "coordinates": [
          35.13865150847007,
          31.78973146789453
        ]
      },
      "objects": [
        {
          "id": "7028d457-5ff0-4071-ac86-ad8514d03d80.473f29a1-bec3-4cb8-99d7-ee50e20ac176",
          "objectType": "editProposalEdit"
        }
      ]
    }
  ]
}

My guess is edits were made before trying to address the suggestion. Have you reached out to NissimAcheroff5 and asked them to remove it?

I didn’t reach out to the user to remove their Edit Suggestion. My thinking is that the ‘no permissions’ error on the ES popped up because I had split the segment it was attached to – essentially, the original segment removed from the map. After a page refresh, the ES itself threw that error. This feels more like a system’s intended behavior that needs looking into (as a non-local bug). IMO, splitting a segment shouldn’t prevent us from resolving ESes tied to original segments that are removed from the map. I’ll file a separate suggestion for it.

I agree with you completely. Cutting a segment breaks the suggestion and we should be able to then remove it when the segment ID it was associated with is no longer available. We brought it up with our SCM and have a sheet to add these to so devs can remove them.

I don’t think this is a bug, but rather something devs didn’t think about.

I just added a suggestion on uservoice.

Hi @r0den,

Thank you for your input. I attempted to reject the suggestion and could not do it in WME Production, so decided to try it in Beta as well and the suggestion was rejected.

Thank you @turbomkt for creating the suggestion.

@r0den please let me know if you see any further examples so we can review them.

Kind regards,
Olesya

Hi @r0den,

I hope you are well,
The suggestion raised by @turbomkt has been implemented, so this issue should no longer be relevant—can you please confirm?

Thank you and regards,
Olesya

Hi @Olesya-Staff, thank for the update.
I don’t have any ESs of this kind now, but I’ll sure post back here if the issue persists after the suggestion’s implementation.

Thank you @r0den, I’ll be awaiting your feedback.

Best,
Olesya