Skip to content
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

6.0 Feedback: "Clear Unavailable robots list" does not display confirmation modal #10511

Closed
reachojhaneha opened this issue May 27, 2022 · 2 comments · Fixed by #10648
Closed
Assignees
Labels
6.0-feedback Feedback for the 6.0 release

Comments

@reachojhaneha
Copy link
Contributor

Overview

Clicking on "clear unavailable robots list" is an incomplete experience for the user

  • app doesnot respond if the unavailable robots were cleared or not
  • if the unavailabel robots are not available - clicking on this button will not solve any purpose

There are designs for this button

Current Behavior

Screen Shot 2022-05-27 at 1 02 16 PM

Expected Behavior

Screen Shot 2022-05-27 at 1 02 36 PM

Steps To Reproduce

  1. Goto Advance tab in app-settings
  2. Click on "Clear Unavailable Robots list" -> user gets no response from the app

Expected designs are not yet implemented

Operating system

No response

Robot setup or anything else?

No response

@reachojhaneha reachojhaneha added the 6.0-feedback Feedback for the 6.0 release label May 27, 2022
@nusrat813
Copy link

Adress after beta

@mikecardarelli mikecardarelli changed the title 6.0 Feedback: "Clear Unavailable robots list" doesnot displays confirmation modal 6.0 Feedback: "Clear Unavailable robots list" does not display confirmation modal Jun 1, 2022
@koji koji mentioned this issue Jun 6, 2022
14 tasks
@jerader jerader self-assigned this Jun 7, 2022
@y3rsh
Copy link
Collaborator

y3rsh commented Jun 7, 2022

still on alpha1
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.0-feedback Feedback for the 6.0 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants