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

Select a quiz - Possible confusion caused by the 'Changes saved successfully' message #12333

Closed
pcenov opened this issue Jun 20, 2024 · 2 comments · Fixed by #12389
Closed

Select a quiz - Possible confusion caused by the 'Changes saved successfully' message #12333

pcenov opened this issue Jun 20, 2024 · 2 comments · Fixed by #12389
Assignees
Labels
P1 - important Priority: High impact on UX

Comments

@pcenov
Copy link
Member

pcenov commented Jun 20, 2024

Observed behavior

Observed while testing #12312 - When I select a quiz I see the 'Changes saved successfully' message. If I decide to close the modal, then I see a confirmation modal informing me that "You will lose any unsaved edits to your work". Since I don't think that I have unsaved edits I go ahead and click 'Continue' which results in actually losing the entire quiz.

A similar confusion can occur even when creating a quiz from scratch as I might have entered the title of the quiz and just added some questions in which case I will also see the 'Changes saved successfully' message prior to exiting the quiz.

Video:

Changes.saved.successfully.message.mp4

Expected behavior

It should be further discussed how to convey to the user clearly whether the entire quiz is saved or just some modifications made to the sections.

Steps to reproduce the issue

  1. Install the build from First pass string updates following UX writing and ditto review #12312
  2. Observe the steps in the provided video.

Usage Details

Windows 11, Ubuntu 22 - Chrome

@pcenov
Copy link
Member Author

pcenov commented Jun 20, 2024

@radinamatic

@rtibbles rtibbles added the P1 - important Priority: High impact on UX label Jun 20, 2024
@rtibbles
Copy link
Member

I think the simplest solution here is simply to only show this snackbar when changes have actually been saved - i.e. when the 'save' button has been clicked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 - important Priority: High impact on UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants