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

Add error message and update saving message for plan writing #3232

Merged
merged 10 commits into from
Oct 16, 2023

Conversation

pengyin-shan
Copy link
Contributor

This ticket is created as an improvement for a user's plan-saving problem. The user so far only sees 'Saving...' and 'Answered by...' messages after saving the plan successfully.

However, a user of DMP Assistant was stuck on the 'Saving' message and no explicit guidance showed that if the user turns to other tabs now, the content in the rich text box will be lost and unrecovered. So she lost all her inputs of plan content.

Thus:

  1. We need to add an error message in the error-saving span. We used to have nothing in it.
  2. We need a more explicit expression of telling the user to save the plan to a separate file if an error occurred in this process. So the user won't feel misled and fresh this page then lose all input.

Changes proposed in this PR:

  1. For error message:
    Screenshot 2022-11-08 at 2 31 13 PM
  2. For saving... message (very long, but users normally skim through it if their plan is saved successfully, so it won't affect regular user experience)
    Screenshot 2022-11-08 at 3 12 25 PM

Please let me know if you have any suggestions for these messages!

Copy link
Contributor

@briri briri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me @pengyin-shan I just have a small comment on the wording of one of the messages. I think it might be useful to run it by the PMs

<span class="label label-warning status" style="display:none;" data-status="saving">
<%= _("Saving...Please do not refresh or go to another page!") %>
<br><br>
<%= sanitize(_("If you stuck on this message, please save your plan to a separate file and contact us at %{helpdesk_email} .") % {
Copy link
Contributor

@briri briri Nov 9, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "If you are stuck on this message" might be confusing since it doesn't let them know what is supposed to happen (e.g. how long is 'stuck'?).

Suggest we change the messaging (maybe ask the PMs)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "If you are stuck on this message" might be confusing since it doesn't let them know what is supposed to happen (e.g. how long is 'stuck'?).

Suggest we change the messaging (maybe ask the PMs)

How about "If this message doesn't disappear in 1 minute?" @mariapraetzellis how do you feel?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mariapraetzellis @dsisu : one more UI message suggestion is needed. For anyone sticking on the 'Saving...' message because of a system problem, we need them to remember not to fresh the page and to contact the helpdesk immediately.

Instead of saying If you are stuck on this message, please save your plan to a separate file and contact us at %{helpdesk_email} , any suggestions you have?

@briri
Copy link
Contributor

briri commented Jan 23, 2023

@mariapraetzellis @dsisu can you have a look at the wording for these messages and let us know what would be appropriate?

@pengyin-shan pengyin-shan changed the title User experience improvement: add error message and update saving message for plan writing Add error message and update saving message for plan writing Feb 27, 2023
@pengyin-shan
Copy link
Contributor Author

The PR is ready as long as the PM agrees with the final version of the message. Once they reach the final decision, the developer can just update the messages in app/views/answers/_status.html.erb and it should be done.

I added CHANGELOG already, and updated Github actions to use node 16 so all test pass.

@dsisu
Copy link

dsisu commented Mar 1, 2023

Apologies for not responding sooner. Am I too late?

Which screens are we talking about exactly, at which point in the process of writing a plan are these messages meant to appear? Thanks.

@pengyin-shan
Copy link
Contributor Author

Apologies for not responding sooner. Am I too late?

Which screens are we talking about exactly, at which point in the process of writing a plan are these messages meant to appear? Thanks.

These messages are supposed to show when saving the plan is not work as expected. We used to have users stuck on saving plan, but we didn't give any error message, so the user refreshed the page and all answers are gonna. We want to prove this situation because user will lost all the inputs.

@martaribeiro martaribeiro merged commit 9ab03b7 into development Oct 16, 2023
5 of 7 checks passed
@martaribeiro martaribeiro deleted the add_error_message branch October 16, 2023 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants