-
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
[watcherUI] The "count" of watches deleted can be confusing to the user. #17956
Comments
Original comment by @ycombinator: The message says (emphasis mine) "out of 2 selected watches" specifically to avoid this ambiguity. Still, if you overlooked the "selected" in the message then a user might too and I can see how they would end up having the same confusion that you did. Perhaps there is even better verbiage we could use here. @debadair @snide @skearns64, any suggestions? |
Original comment by @snide: You likely don't need the "selected" part in the text. Just saying "Successfully deleted {num} watches" is enough. Seems like something you'd use a toaster system for. Assume we don't have one of those? From your screen it looks like this pops in the header above the breadcrumbs? cc @cjcenizal since we'd talked about toasters and alerting previously. |
Original comment by @ycombinator: Thanks @snide. We'll change this to simply "Successfully deleted {num} watches" for successful deletes and "Failed to delete {num} watches: {error}" for (unlikely) unsuccessful deletes. BTW, this is using the toaster notification that drops down from the top of Kibana. Its probably not as obvious in the screenshot. |
Original comment by @cjcenizal: @snide Yeah this is exactly why I created LINK REDACTED This notification you see here is our only notification system, and it's kind of rough around the edges (e.g. it pushes all content down when it shows up, and isn't a good fit for many notification use cases). |
Original comment by @ycombinator: For the scope of this issue we will simply be changing the text. When the new notification system is in place, we'll create another issue to start using it across the Watcher UI. |
Pinging @elastic/es-ui |
Original comment by @Rasroh:
Steps to reproduce:
cc / @ycombinator @jim
The text was updated successfully, but these errors were encountered: