Bug 1470697 - [unified-registration] Unclear which values are required
[unified-registration] Unclear which values are required
Product: OpenShift Online
Classification: Red Hat
Component: Accounts and Billing (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Mike Dame
: OnlinePro
Depends On:
  Show dependency treegraph
Reported: 2017-07-13 09:33 EDT by Will Gordon
Modified: 2017-10-16 08:56 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Will Gordon 2017-07-13 09:33:03 EDT
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):

How reproducible:

Steps to Reproduce:

Actual results:
No indication about required fields

Expected results:
Clear indication of required fields

Additional info:
Comment 1 Abhishek Gupta 2017-08-18 09:52:00 EDT
Mike: We will need to address this in the unified registration application.
Comment 2 Will Gordon 2017-10-11 06:52:15 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.