When we stumble upon an error in Google Maps or here on Connect, I’m a little confused about where to report it. Should it be here in How-tos or in Idea Exchange?
Over time Google moderators have moved bug reports eighter way.
Cheers
11 Likes
Good question, @MortenCopenhagen .
Sometimes there is a thin border between reporting a problem (here on how to) and suggesting an improvement (idea exchange).
The place for reporting a bug that need to be fixed is definitely how to. If something is wrong and need to be fixed (e.g. a wrong count, wrong address) this is the place.
An improvement is something different (e.g. I would like a different way for finding my photos) idea exchange is the place where to suggest a change to the team.
In both cases we suggest a chance, but the scope is different: fixing Vs improving.
Hope this can help you. Do you have an example (I am sure you have) about what to ask to the team?
3 Likes
Thanks, @ErmesT .
My current example is here: https://www.localguidesconnect.com/t5/Idea-Exchange/Uploading-video-from-Google-Photos-fails/idi-p/2097036
My question was a tiny bit rhetorical since I experienced Google Moderators not being consistent. So I take that you would have put the above mentioned into How-to. In Idea Exchange we invite others to vote. That could be helpful. But when it is a real bug that just needs fixing - and not so much discussion - I agree it should be in How-tos. So hopefully a Moderator like @sonnyNg will respond and move it tomorrow.
Sorry I did not wait for your guidance 
Cheers
2 Likes
Hey @MortenCopenhagen My two cents is that when it is when some functionality both on Connect or Maps is not working as expected, the correct is “How to” section. However, in some situations, the user is reporting some issue that is not allowed so far.
Let me try to offer an example: if a user is not being able to add a photo on Connect, the How to Section would be the best section to that. However, if the same user is trying to add a 360 photo, maybe the idea exchange would be a better option once we know that it is not possible to do it so far.
Makes sense?
My best!
1 Like
Hehe, @MortenCopenhagen
You are right, your issue should be on how to. But, let say for a moment, what if you post was “developing a better tool for uploading photos on Google Maps via desktop”?
Same for the 360, @AlexandreCampbell .
Not being able to embed a 360 in connect is not a bug, but a specific choice, due to security concerns. So definitely, a proposal for an interface between Maps and connect for picking the 360 without using I-frame can be an evolution, to be suggest on Idea exchange
2 Likes
Thanks @ErmesT and @AlexandreCampbell .
An easy to remember rule could be:
Bugs that needs fixing to restore privously existing functionality should be in How-tos.
New features and improvements beyond existing functionality should go in Idea Exchange.
Is that usable?
3 Likes
I see @ErmesT . What I meant is that a person can report it as a bug, thinking that it would be possible. BTW, I took 24 minutes to try to find an example and let my box answer open, so I didn’t notice that you had already answered @MortenCopenhagen with a better one hehe
3 Likes
Hi everyone,
Much appreciated for the interesting subject! : ]
As @MortenCopenhagen shared the inquiry, it is much appreciated from @ErmesT and @AlexandreCampbell for providing straightforward information on the regard!
How-tos would indeed be handy in the situations either guidance towards instructions for specific procedure or pointing out a specific irregularity/issue on Connect or Google Maps and other. (examples of the issue and more often updates would be shared, I would say the posts there are usually bulkier)
Should a Local Guide post on the Idea Exchange board, when the user after gained some observations that may improve and have it as feedback towards some functionality of the program, with specifically pointed out modifications.
I will make sure to have idea checked, MortenCopenhagen, thanks for letting me know as well!
2 Likes