Skip to content

No specific UI feedback on "Display name" missing while creating a new user, except for save button being disabled #2105

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

Closed
rowasc opened this issue Oct 4, 2017 · 13 comments · Fixed by ushahidi/platform-client#1453 or ushahidi/platform-client#1486

Comments

@rowasc
Copy link
Contributor

rowasc commented Oct 4, 2017

Expected behaviour

  • I see an error/warning letting me know that I have to fill in the display name.
  • Error text: "Display name is required" (ie: like all other required fields)

It should look like this:
Image of the display name and error correctly shown

Actual behaviour

I don't see an error or warning unless I edit the display name field and delete the content.

Steps to reproduce the behaviour/error

  • Login as an admin
  • Go to settings/users
  • Click on + to add a user.
  • Fill in email and password.
    • The save button is disabled, but I don't know why.

Aha! Link: https://ushahiditeam.aha.io/features/PROD-515

@rowasc
Copy link
Contributor Author

rowasc commented Oct 4, 2017

screen shot 2017-10-04 at 11 38 37 am

Not a blocker, but it's really confusing if you don't realize the display name is there and required.

@rowasc
Copy link
Contributor Author

rowasc commented Oct 4, 2017

cc @jshorland probably low priority considering all things, but still a weird behavior, I think

@jshorland jshorland added this to the UX clean up milestone Oct 4, 2017
@zube zube bot removed the Backlog label Jan 29, 2018
@rowasc rowasc removed this from the UX clean up milestone Sep 13, 2018
@rowasc rowasc added P2 - Normal Hacktoberfest Issues open to folks participating in hacktoberfest labels Oct 5, 2018
@rowasc rowasc added Community Task Issues that the Ushahidi OSS community is encouraged to contribute to and removed Community Task Issues that the Ushahidi OSS community is encouraged to contribute to labels Oct 29, 2018
@Angamanga Angamanga added good-first-issue Issues that are ideal for first time contributors to OSS or first time contributing to the platform and removed Hacktoberfest Issues open to folks participating in hacktoberfest labels Mar 14, 2019
@NidhiKJha
Copy link

NidhiKJha commented Mar 24, 2019

@Angamanga This issue appears to have been fixed.
It issue should be closed.
Screenshot from 2019-03-25 00-34-54

@rowasc
Copy link
Contributor Author

rowasc commented Jun 11, 2019

Thanks, @NidhiKJha for checking this :)
I think this is only fixed in the JS rewrite branches. Sadly It's still happening in master (production) so it needs to remain open
Screen Shot 2019-06-10 at 22 05 47

@Angamanga Angamanga added the Needs: description Tagging issues to add better descriptions for the community label Jun 11, 2019
@Erioldoesdesign
Copy link

Would love to see this in prod :)

@rowasc rowasc added Codebase: Client Indicates issue work will be in client WSC and removed Needs: description Tagging issues to add better descriptions for the community labels Aug 16, 2019
@rowasc
Copy link
Contributor Author

rowasc commented Aug 17, 2019

This issue is still open to be fixed (noting for future contributors) . thanks 🎉

@rowasc rowasc removed the wsc2019 label Aug 19, 2019
@rowasc rowasc added the Hacktoberfest Issues open to folks participating in hacktoberfest label Sep 28, 2019
@noone0212
Copy link
Contributor

Hello @rowasc , Can I work on this issue? Will be my first bug to work upon!
Also what files should I see to get started with solving the issue?

@rowasc
Copy link
Contributor Author

rowasc commented Feb 25, 2020

Hi, thanks for reaching out. Yes you can totally work on this , thank you so much.

  • The code for the user settings section can be found in ./app/settings/users
    You may want to look at the users-edit file in that dir for this specific issue. I think probably the best solution is that if the form itself is dirty/has changed and that field is empty, we indicate that field (name) is missing. The way it works right now the user is totally stuck without any clue of what's happening 😬

Another thing that would be useful is showing an asterisk for required fields as we do for posts.
Screen Shot 2020-02-25 at 15 59 02

cc @Angamanga FYI

@rowasc
Copy link
Contributor Author

rowasc commented Mar 30, 2020

@Obadha2 this needs QA (in steve)
Thanks!

@AmTryingMyBest
Copy link
Contributor

@rowasc while all required fields are highlighted, there's no feedback if "Display Name" is missing. There's no response when user clicks Save.
Doesn't pass QA.

@Angamanga
Copy link
Contributor

@rowasc @Obadha2 This one is a bit tricky:

  1. All the fields are required in order to activate the save-button.
  2. When adding a new user, the display-name is empty
  3. The validation only check touched fields, since we don't want to show an ugly error-label before the user starts typing
    So if the user doesn't add anything to display-name, the label cannot be seen. If the user adds something and then deletes it, THEN the error-label is shown.

This fix is a good start since it at least shows an asterisk on the required fields. We could add a new issue about activating/disabling the save-button (probably happens in more places too). We really want to move away from that anyway since its not accessible 🎉.

@rowasc
Copy link
Contributor Author

rowasc commented Apr 1, 2020

alright. Then I think this improvement can go live, and we need to work on a more accessible solution as a second step, as Anna mentions. I think disabling the button is not the best idea without providing feedback.

EDIT: let's leave this one open actually, it contains all the history (even if we release the current fix) and covers what we are discussing no?

@Angamanga
Copy link
Contributor

@rowasc Yes, lets keep it open, I will take a look at and spec it further today!

@noone0212 noone0212 removed their assignment May 4, 2020
@rowasc rowasc added this to the Parking Lot milestone Sep 4, 2020
@rowasc rowasc modified the milestones: Parking Lot, Hacktoberfest Sep 30, 2020
@Angamanga Angamanga removed this from the Hacktoberfest milestone Oct 1, 2020
@Angamanga Angamanga removed Community Task Issues that the Ushahidi OSS community is encouraged to contribute to Hacktoberfest Issues open to folks participating in hacktoberfest good-first-issue Issues that are ideal for first time contributors to OSS or first time contributing to the platform labels Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment