-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add reset project Button to allow users start over completely (Issue from Usability Testing) #868
Comments
David agrees with adding a start over button |
I'm starting on this one. |
Progress: added the Reset Project button. |
From tonight's meeting, on reset project |
@fyliu please add a level label to this issue (choices are easy, hard, medium). The choice should be based on the POV of a product manager who would add this label as a way of guiding developers on the team to choose increasingly harder issues. |
Progress: ETA: |
Writing the tests took longer than I thought. Screenshots are in the linked PR. Both logged in and not logged in cases should reset. Canceling the reset modal should keep the unsaved changes. |
Hi @fyliu - do we still have this implemented just as a button on the top of page 2? - I believe we should add a button to the bottom of all pages on this instead, but I will bring this up again tonight, and work look into anything else we need. |
@KPHowley sure. I'll add a task item to put it at the bottom. We might need to ask UX members about putting it left or right of the save button. |
we actually have a mockup which shows a start over button already... https://www.figma.com/file/nD9QK56Mzq7xNSaSUoeGx0/?node-id=2626%3A11673 |
Pushing this issue through so we could show it to stakeholders sooner while waiting for the design of the button as a new issue |
LADOT accepted the design changes. |
@ExperimentsInHonesty I need clarification. The reset button should be on the top or the bottom? |
Demoed to Stakholder (Dave/Alexander) |
Overview
One of the issues that were raised during usability testing (row 2) was that users were unsure how to start over completely
Possible Solution
The text was updated successfully, but these errors were encountered: