Red Hat Bugzilla – Bug 1470697
[unified-registration] Unclear which values are required
Last modified: 2018-03-05 13:19:14 EST
Description of problem:
When updating profile in the accountant for Pro on https://account.openshift.com/app/register/profile, there is no indication which values are required, and just prevents the user from moving forward.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
No indication about required fields
Clear indication of required fields
Mike: We will need to address this in the unified registration application.
The greeting dropdown is not marked as optional, meaning I would think it's required.
Before all required fields are filled out, the "Save Profile" button is in a "disabled" state. I had only now realized that I could click on it to determine which values I was missing.
Based on the conversation in #aos_online and the guidelines in https://blog.patternfly.org/required-fields/, I can understand not using * for every field.
However, maybe we shouldn't change the submit button state, making it more obvious that users can click on it...and *then* be directed to the required field.
Having been tried in manage.int.openshift.com, the features could work well according to the description in PR https://github.com/openshift/online-registration/pull/647.
But from QE side, we don't think it was very friendly. Because customers could not know which was essential to fill in before they clicked the "Save Profile" button. So we recommended highlighting the essential blank directly till it was filled in. So that customers could easily know the essential blank without having to click the button.
How do you think that?
That is probably acceptable, since 99% of the time most of the fields will already be pre-filled with data from streamline.
I agree with Tim on this one. I appreciate seeing the boxes now marked as optional...and the "Please fill out this field." message clearly shows while clicking/tabbing through the fields. I would consider this a marked improvement over the previous functionality!
OK, thanks, I could accept that.