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

UI Design: Preferred Name #18168

Closed
steveburtch opened this issue Oct 13, 2023 · 3 comments
Closed

UI Design: Preferred Name #18168

steveburtch opened this issue Oct 13, 2023 · 3 comments
Labels
BTR Business Transparency Register Register BO UX User Experience Research & UI Design

Comments

@steveburtch
Copy link

We need an additional name field to allow users to enter a "preferred name" so that people who do not use their full legal name to identify themselves can do so.

Question: do we go with Preferred Name or Nickname or ??
Take recommendations to RAID?

Instructions

  • single name field
@mstanton1
Copy link
Collaborator

Note: a change was logged under https://app.zenhub.com/workspaces/relationships-team-space-new-649992c7f903a02c9b33009f/issues/gh/bcgov/entity/3564 to add a preferred name option in the auth flow. From a user flow perspective it's likely preferred to leverage what they've already provided, rather than have the same "preferred name" entered twice.

Auth work is yet to be scheduled.

@steveburtch
Copy link
Author

@mstanton1 We've already added the preferred name field to the SI standalone filing. I think this design was done a while back but the ticket stayed on the board. It should be closed, although we may want to review what Relationships has done or is planning.

@mstanton1
Copy link
Collaborator

Understood. We can leave it as is, and close this given the work is done. I'll keep it in mind to revisit when auth implements a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BTR Business Transparency Register Register BO UX User Experience Research & UI Design
Projects
None yet
Development

No branches or pull requests

3 participants