Skip to content

Add feedback widget #1885

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

Closed
4 tasks
Tracked by #1939
ketang opened this issue May 29, 2022 · 13 comments · Fixed by #2447
Closed
4 tasks
Tracked by #1939

Add feedback widget #1885

ketang opened this issue May 29, 2022 · 13 comments · Fixed by #2447
Assignees
Labels
needs decision Needs a higher-level decision to be unblocked. site Area: frontend dashboard
Milestone

Comments

@ketang
Copy link
Contributor

ketang commented May 29, 2022

What is your suggestion?

Add a live feedback widget e.g. Intercom to the web UI.

Why do you want this feature?

So users can provide direct feedback.

Are there any workarounds to get this functionality today?

Emails, Discord, GitHub issues, etc., but none are in product.

Are you interested in submitting a PR for this?

No.

Implementation Ideas:

This could start as something as simple as a link to a prefilled github template OR a service for feedback collection

See also the VSCode approach for feedback as suggested by @oxy

Implementation Decision (for first iteration):

  • Add link text in footer to the right of the version with the copy: "Submit feedback"

Add Feebback link here

  • this should open an minimalist template in Github in a new tab
  • The version should auto populate into the form
  • The users can enter whatever text they want from there
@tjcran tjcran added this to the Community MVP milestone May 30, 2022
@ammario
Copy link
Member

ammario commented May 30, 2022

If this is done, it should be less intrusive than your run of the mill persistent chat icon in the bottom right corner. Dev Tools / Infrastructure products (maybe any that cater to the technical audience) do not have this kind of persistent widgets.

I speculate these reasons:

  • Open Source Software prefers to accept feedback via the public tracker
  • Developers have a lower tolerance for bloatware, UI noise, and threats to their privacy

There's also the fact that a chat widget would be awkward in our industrial design.

A callout in the footer to file an issue with any feedback seems like a good way to solve the problem.
image

@ketang
Copy link
Contributor Author

ketang commented May 30, 2022

This seems like a great opportunity for using an A/B testing tool, not just so we can see what works best but also in order for us to be able to adjust the amount of feedback that we're getting at any given time. If we're getting too much, we can show it less prominently less often to fewer users. If we're getting too little, we do the opposite.

@misskniss misskniss added site Area: frontend dashboard nice-to-have needs decision Needs a higher-level decision to be unblocked. labels May 31, 2022
@ammario
Copy link
Member

ammario commented May 31, 2022

To be clear, you're OK with a link to file an issue?

@ketang
Copy link
Contributor Author

ketang commented May 31, 2022

I would like to try multiple things. That can be the first.

@misskniss
Copy link

Made this an Epic since it is going to have multiple parts.

@ammario
Copy link
Member

ammario commented Jun 1, 2022

@misskniss what parts were you thinking? In my mind this was an a link to file a new GitHub issue somewhere in the product.

@tjcran
Copy link

tjcran commented Jun 1, 2022

Let's start really simple. It's an OSS product and feedback should go into Github. Let's provide an in-app "widget" that takes them right to a new issue form in Github. Per discussion with Ammar/Kyle live.

@misskniss misskniss removed the epic label Jun 3, 2022
@kylecarbs kylecarbs changed the title Feat: add feedback widget Add feedback widget Jun 7, 2022
@Kira-Pilot Kira-Pilot assigned Kira-Pilot and unassigned greyscaled Jun 16, 2022
Kira-Pilot added a commit that referenced this issue Jun 16, 2022
Kira-Pilot added a commit that referenced this issue Jun 17, 2022
* add ability to activate users

resolves #2254

* added test

* PR feedback

* guarding against null validation_contains field

* fixing type for ParameterSchema

resolves #2161

* added report link to footer

resolves #1885

* added test

* Footer story

* fix broken test
@tjcran
Copy link

tjcran commented Jun 17, 2022

One note: I think this should actually be wider than "reporting an issue" aka bugs. I think we should also be using this to gather feedback and feature requests as well.

@Kira-Pilot
Copy link
Member

@tjcran given that we're going with a link, what sort of language do you think we should use? Maybe something like 'Report an issue or share feedback"?

@tjcran
Copy link

tjcran commented Jun 17, 2022

@Kira-Pilot i think the or statement is fine since the whole thing is pretty small. Can you also clarify what is the square to the left of the words?
image

@Kira-Pilot
Copy link
Member

@tjcran it's a little beetle (for bug). Did you grab that screenshot from chromatic/storybook?
Screen Shot 2022-06-16 at 7 25 11 PM

If it's too cutesy or if its not showing up for you IRL, I can definitely take it out.

@tjcran
Copy link

tjcran commented Jun 17, 2022

@Kira-Pilot my screenshot was from dev.coder.com and it is not showing up there. I like it. but doesn't seem to be working.

@Kira-Pilot
Copy link
Member

@tjcran as discussed, seems to be a windows issue. I will take out for now and adjust wording. In the future, we can add a small png if we feel like we need more pizzazz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs decision Needs a higher-level decision to be unblocked. site Area: frontend dashboard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants