Feedback is not really a feedback

[trailmax]

When using Help -> Send Feedback, I'm redirected here where I'm encouraged to submit an issue. But not all feedback are issues. In this particular instance I wanted to say "thanks and good job for implementing X" (as a developer, I know it is nice to get this kind of feedback!). But that is not really a format for GitHub Issues.

Would it be possible to restore the old way for collecting feedback? When I'm not dipped into a hot end of technical stack and need to browse through a pile of already existing issues - very discouraging.

Or at least rename "Send Feedback" into "Report Issue".

[JakeRadMSFT]

Thanks for your feedback! :)

You're right and it's something we struggled with when we switched to GitHub for "Feedback". We're happy to accept all feedback here ... issues or not!

One of our motivations for changing is that keeping up with the many laws of Managing Data isn't a cheap responsibility. We've decided to relinquish that responsibility to GitHub for Feedback and Issues.

Most of our motivation though is to encourage users to help each other and give a public way to provide workarounds while we try to ship fixes and features.

So although, I think GitHub is the perfect spot for issues. I agree it's not the best for feedback but we're not going to restore the old way due to GDPR - European laws around managing data. With GitHub your data is more transparent and how we use that data is more clear too. Unfortunately, with "The Old Send Feedback" - it's not 100% clear where that Data goes or how users could "Unsend".

[JakeRadMSFT]

That being said ... I'll see if we have somewhere we can point people to for praise or review! Leaving the issue open to see if we (Microsoft) already have an offering.

[JakeRadMSFT]

How would you feel about two menu items ... Report Issue that brings you here and Send Feedback which sends you here: https://feedback.azure.com/forums/217298-storage or somewhere similar?

[trailmax]

@JakeRadMSFT in this case it is totally appropriate to say that data protection has gone MAD - totally off the rockers! Damn that vague GDPR law!

I've tried to find an example of how feedback is collected from VS or VSCode and both have changed recently. Though VS Code has almost got it right:

Not 100% sure that using Twitter is fully appropriate (what if I don't have a Twitter account? Or I'm a recovering ex-Twitt-addict?).
But sending a smile or sending a frown worked pretty good for me when piloting previews of Visual Studio. Don't know how these were stored and how these were processed, but a I did send a fair amount of smiles/frowns and bugs for VS.

What you propose with 2 links can work - worth a shot.

[trailmax]

By the way, the feedback I wanted to send was about "Update on close" - when the update of the application is executed after I close the app, not on startup. Makes it easier to update it without having to break my flow. Thanks for listening (I did send a feedback about that a while ago) and implementing!

[craxal]

VS used it's own feedback database for collecting that data. Incidentally, we were using the same database to collect Storage Explorer feedback. Sadly, that database has been shut down. We even had a period where we stopped getting user feedback, and that was because we hadn't been informed of the shut down!

[trailmax]

@craxal OUCH! That sounds like internal communication nightmare

[MRayermannMSFT]

We don't mind y'all sending feedback, positive or negative, via GitHub. We understand that posting feedback in a section called "issues" might seem confusing, but at this time we're trying to keep all customer communications focused here/in this area.