Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

HATS driven user/session exploration to identify progression/regression over the dev17 releases #65232

Closed
arunchndr opened this issue Nov 4, 2022 · 3 comments

Comments

@arunchndr
Copy link
Member

arunchndr commented Nov 4, 2022

Ask #1:
I think first order of business is to validate if the completion, lightbulb and error list goals are downtrending based on our telemetry and dashboards. If not, we can define goals there to improve. If there are no data/dashboards, @Cosifne's current work on telemetry and dashboards should help and we can continue pushing to expand on scenarios.

Ask #2:
Here are the HATS survey verbatims - https://microsoft.sharepoint.com/:x:/r/teams/VisualStudioProductTeam/Shared%20Documents/Dev17%20VS%20Perf%20Epic/Planning/17.3%20Performance%20Feedback.xlsx?d=w42fc4a9a440149d2b7a0c1fdad5eced1&csf=1&web=1

The ask here is to reverse engineer the verbatims to session id to see if there are known problem areas across 3 features spaces to present the identified problems back to the Platform team.

  • completion
  • lightbulb
  • error lists
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Nov 4, 2022
@arunchndr arunchndr removed the untriaged Issues and PRs which have not yet been triaged by a lead label Nov 4, 2022
@arunchndr
Copy link
Member Author

Tagging both @genlu and @mavasani to this to perform initial exploration.

@CyrusNajmabadi
Copy link
Member

Closing out as speculative.

@CyrusNajmabadi CyrusNajmabadi closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants