-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Design] User feedback link to Discuss #29247
Comments
Pinging @elastic/apm-ui |
Related PR #29457 as local nav changes have been implemented, the feedback link as it's currently positioned will be placed top left like this; In my opinion we need to find a more appropriate solution for K7 than placing the link in the local navigation, at least like this. @cchaos @snide I know you are swamped with details before release, but would it be possible we could talk 20-30 mins about this later today or tomorrow? Would like to know where you might stand on a solution for this. |
@formgeist I can meet whenever. However, either of your ideas in the summary could work. I just don't know if there is any setup that allows apps to add into the Kibana header. The sidebar approach would work too, but I'd just make it a regular text link "APM Feedback" that sticks to the bottom of the sidebar instead of a floating button. |
Adding to this... The Canvas team used to have a similar feedback mechanism that sent an email though I don't recall where it was placed in the UI. There has been talk in the past week of potentially bringing it back which makes me think the solution should be universal. In other words, perhaps it could be something you control via a plugin setting (e.g. a url or email address) where if it exists, then we show a button in the header or side nav. |
@ryankeairns Having this as a core plugin feature would be nice! |
@ryankeairns Thanks for adding the Canvas view on this. I would also expect that the Codesearch team (cc @daveyholler) would have such a need to get feedback at least for the first few iterations of their solution. |
Replaced by #29664 |
#29664 has been merged. You can check the PR summary for how to tap into that help item to add your feedback button. |
Awesome job sneaking this stuff in so quick. Good job everyone! |
@cchaos Excellent! Thanks again for getting this in so quick 💯 |
Summary
Related to #29087, in preparation to move away from the old Kibana header, the APM app features a small but valuable option to inform users that we have a discussion forum where they can voice feedback and suggestions to the product. This feature is also present in Uptime, but I imagine will also be added to several other solution apps in Kibana.
For consistency across multiple apps and multiple views, it makes sense to show this option in the same place and position at all times. This naturally limits the placement to a few options.
Proposed solutions
Pre-K7 header
Related issue #29349
We implement the feedback option like in APM, in the top menu bar with a similar panel to show the copy and link. We can choose to change the design to possibly show a popover instead of the much more intrusive panel that is currently being displayed.
Post-K7 header
As we do away with the menu bar, breadcrumb is moved to the global header, the datepicker is set within the app itself. This means we have to find a new placement for this feedback option in the UI.
Kibana global header
One option could be to offer apps to enable a feedback button in the global header with copy and link to the Discuss forums. We'd like to deep-link to the specific app forum, so users won't have to do the digging themselves.
In-app placement
Another option would be to create a floating component that sits inside the app content area, which is most recognizable from other services such as Intercom and others where there's a floating icon button on the page. In this case it is positioned bottom left to avoid conflicting with toasts and most content on the page (when there's enough margin).
cc @elastic/kibana-design for your consideration and feedback
The text was updated successfully, but these errors were encountered: