-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ObsUx] Standardize the button for providing feedback. #174719
Comments
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
@kpatticha Thank you for adding this issue! In infra, we have different Google forms based on the feature used ATM ( so we added those buttons separately and we also have a different form/button label in case K8s pods are selected in the I think the idea of Google Forms is to collect feedback and contact details in case the user wants to chat with us about the product and their use case. I am not sure about the discuss forum. I don't know if we need to add the feedback button on the other infra pages and if there will be any benefit. Logs is a separate thing for example and the settings page is different from APM - it's just a simple single form. |
@jennypavlova thanks for the context. I didn't realize that the top right button could be for specific features as well. As for the discuss forum, I don't know the historical context either. Also, I'm not sure who is monitoring it. |
Hey @kpatticha, I'm not sure how much this helps but the goal of the Google form buttons for feedback was to:
In my experience, the Discuss forums weren't really meeting these three needs and it's been pretty successful so far. I'm conscious about consistency (and also ensuring we don't spam customers with surveys) so any suggestions on how to improve this welcome! Note : I really wish we had some survey software (e.g. HotJar) to help standardise this and ensure we don't spam users but unfortunately we don't :( |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
APM
Screen.Recording.2024-01-11.at.20.27.38.mov
Infra
Screen.Recording.2024-01-11.at.20.54.06.mov
Profiling
Screen.Recording.2024-01-11.at.20.54.21.mov
Proposal
The text was updated successfully, but these errors were encountered: