Feedback component request

[gjones]

There's an issue in the cloud repo around adding a feedback feature. Having looked at it, and seeing that the suggested area to trigger it is the header, which will soon be global across our products, I propose this should be an Eui component.

In short, I think we want a consistent feedback component that works across Cloud, Kibana, Support, and future apps. On the Cloud side, plenty of work has gone into working out exactly how to ingest, and what to do with the data on the backend. I don't believe thats something that this component should be worried about, but its open to discussion.

I've just pasted @cristina-eleonora's initial suggestion in here, but there's plenty more context in the linked issue.

General feedback

• Personalized message in the text box
• Offer the opportunity to join Elastic UX Labs

Feedback regarding the current page

• Mention the page name in the radio button
• Personalized message in the text box
• Offer the opportunity to join Elastic UX Labs
• Let them rate the page

IDEA: depending on how they rate it, we can personalize the message inside the box.

Same page once the user rated the page using the emojis:

Technical issue

• hide text box
• disable or hide Send button
• offer a link to the support page

@cchaos @snide

[gjones]

As @ryankeairns points out, there's a similar request in Kibana elastic/kibana#62489 and I know Ent. Search have been working on their own feedback system so I think its important we ensure we're aligned and collaborating.

[cchaos]

Not only ins Ent Search working on a similar system, but I believe there is a working group concentrating on a pattern for this. If this is an effort that will be spanning all our products, I think it's important that those who are currently working on the pattern to get input from all area teams as to what their needs are.

This is one of those "components" that will indeed act more like a pattern since every solution's needs will be different. Once the working group has finalized an initial pattern/spec we can certainly start building something in EUI.

@brianearwood & @daveyholler Can you meet with @gjones and @ryankeairns to gather intel on their needs and see where you're aligned?

[daveyholler]

Absolutely. We had a very brief conversation about the possible overlaps a few weeks back. I'll set something up on the calendar for this week to chat through it all in more detail. In the meantime, here's a link to the prototype we have for the component. The use cases are slightly different than what's outlined above, however I believe we can align much better on the solutions for these needs.

Lil Prototype

[elizabetdev]

Just adding the latest design that @cristina-eleonora shared during a zoom meeting: Figma design.

Right now the team is trying to figure out:

• When feedback is submitted, where does it stored so that it's actionable by PMs and designers?
• How is the component registered and fired within Kibana and Cloud in a way that ensures users aren’t being spammed with requests for feedback all over the place?

Apart from that. I think we can start thinking about the front-end.

The component can take two forms:

• A modal
• A toast

In EUI we have those two components (modal and toast). So we need to think if this feedback component is going to be a EUI template/pattern or if we just need to provide the non-existing sub-components like the emojis?

Any thoughts?

CC @ryankeairns @daveyholler @cristina-eleonora @cchaos

[ryankeairns]

For context, there are a number of items currently blocked until a secure connection + APIs can be established to serve data between Cloud and Kibana (deployment and profile links, deployment switcher, nav/global search, profile links, notifications center, etc.). This particular item, while desirable on the Kibana side, has not been a topic of recent discussions, as far as I'm aware, and falls somewhere in the mix of those items.

To put that another way, the prioritization of this feature is uncertain for Kibana. If Cloud is looking to proceed, then we could provide input on the design, but the implementation will likely be a ways off.

[cristina-eleonora]

@ryankeairns, to offer some additional context: we met with @alexfrancoeur, @markdecado and @osmanis last Friday to discuss the next steps to making this happen. One of them is finding out where we can store the feedback, as @miukimiu mentioned.

[elizabetdev]

Yesterday I noticed on https://www.elastic.co/guide/en/app-search/current/web-crawler.html that there is a feedback form:

@cristina-eleonora are you also considering this use case? @snide do you have plans to provide a feedback component in the new elastic docs?

[ryankeairns]

Closing as there is no current product driver for a bespoke feedback component given 3rd party tools can and are filling this need.

[gjones]

😭

[ryankeairns]

Well, well, well. Who do we have here?

[glitteringkatie]

Aw it was Gareth's first discussion!

[gjones]

And just look how it ended.

[alexfrancoeur]

You had me at "Welshman in America"