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

[Enhancement/Feature Request]: Display the first name, last name, and username in dropdown list for adding practitioners to orgs #1519

Open
joyce-x-chen opened this issue Jan 17, 2025 · 1 comment
Labels
Feature Request Used to request for new features that are not available in the current application Needs Scoping Indicates that a ticket needs more scoping

Comments

@joyce-x-chen
Copy link

Use case/Problem Statement

In the Add/Edit team (organization) view, the dropdown list for practitioners only displays usernames.

This is an issue in our shared staging environment since the same username is often repeated across projects. While, ideally, you would not have duplicate usernames in a production project, FHIR Web does not prevent the creation of duplicate usernames. There are also instances where duplicate usernames may exist (e.g. creating a user and then archiving them, then creating another user with the same username).

Since the dropdown list currently only displays the username, it does not provide enough information to ensure that the administrator selects the correct username (if more than one appears in the list). See screenshot example:

Image

Acceptance criteria

In the practitioner dropdown list, display: First Name Last Name (Username)

Project Contact

No response

Relevant Information

No response

@joyce-x-chen joyce-x-chen added the Feature Request Used to request for new features that are not available in the current application label Jan 17, 2025
@peterMuriuki
Copy link
Collaborator

  • Update user creation to capture the keycloak user's username in the corresponding practitioner. That can then be used to generate this options.

@peterMuriuki peterMuriuki self-assigned this Jan 20, 2025
@dubdabasoduba dubdabasoduba added the Needs Scoping Indicates that a ticket needs more scoping label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Used to request for new features that are not available in the current application Needs Scoping Indicates that a ticket needs more scoping
Projects
Status: To do
Development

No branches or pull requests

3 participants