Keith Baumgart
My feedback
50 results found
-
132 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Keith Baumgart supported this idea ·
-
25 votes
Keith Baumgart supported this idea ·
-
65 votes
Hey,
Thank you for this suggestion.
We have added it to our back log. It will take some time. But it will be be solved as part of JB revamp.Thanks
Keith Baumgart supported this idea ·
-
295 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Keith Baumgart supported this idea ·
-
14 votes
Keith Baumgart supported this idea ·
-
477 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Keith Baumgart supported this idea ·
-
329 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Keith Baumgart supported this idea ·
-
14 votes
Keith Baumgart supported this idea ·
-
120 votes
Keith Baumgart supported this idea ·
-
7,206 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Keith Baumgart supported this idea ·
Due to how the quick results show on the client, users will frequently default to choosing those results. Oftentimes it will be a google result which may be incorrectly placed. We can account for that for place points, but when a user is searching for an address we are stuck with adding an RPP and submitting a change to Google for them to change things whenever they get around to it. This creates an issue where in the editor things are correct, but from the user perspective it will not be (even after clearing history)
Allowing this would be a great way to resolve this issue