Enhance Reviewer Search: Support Display Name/Profile Name in Search Field #14436

New Issue

GiteaMirror · 2025-11-02T11:12:55-06:00

GiteaMirror commented

2025-11-02 11:12:55 -06:00

Originally created by @localleon on GitHub (May 2, 2025).

Feature Description

Currently, when opening a new Pull Request in Gitea and selecting the field for assigning Reviewers, the search functionality only matches against the user's username.

In our organization, usernames are cryptic ID numbers (e.g., u4829103), which makes identifying team members difficult. However, users have meaningful Display Names/Profile Names set in their profiles (e.g., Jane Doe), which would significantly improve the identification process if searchable.

Feature Request:

Enhance the Reviewer search input to allow searching by:

username (existing functionality)
display name / profile name (new functionality)

This dual search approach would greatly improve usability for organizations using non-human-readable usernames.

Potential Solution:

We're open to contributing a PR to implement this functionality, pending guidance from the maintainers on preferred design or any potential constraints.

Benefits:

Improves UX by making it easier to find and assign reviewers
Reduces user error in selecting the wrong individuals
Aligns with common expectations from other Git platforms

Let us know if there are any design considerations or existing discussions around this feature. Would you like me to help you draft the initial implementation plan or search if a similar feature has already been requested?

Screenshots

One of the possible could include returning the possible Reviewers in the format "Name (FullName)" like in the edited screenshot below. This would enable with the existing code searching for the FullName in addition to the username

Originally created by @localleon on GitHub (May 2, 2025). ### Feature Description Currently, when opening a new Pull Request in Gitea and selecting the field for assigning Reviewers, the search functionality only matches against the user's username. In our organization, usernames are cryptic ID numbers (e.g., u4829103), which makes identifying team members difficult. However, users have meaningful Display Names/Profile Names set in their profiles (e.g., Jane Doe), which would significantly improve the identification process if searchable. **Feature Request:** Enhance the Reviewer search input to allow searching by: - username (existing functionality) - display name / profile name (new functionality) This dual search approach would greatly improve usability for organizations using non-human-readable usernames. **Potential Solution:** We're open to contributing a PR to implement this functionality, pending guidance from the maintainers on preferred design or any potential constraints. **Benefits:** - Improves UX by making it easier to find and assign reviewers - Reduces user error in selecting the wrong individuals - Aligns with common expectations from other Git platforms Let us know if there are any design considerations or existing discussions around this feature. Would you like me to help you draft the initial implementation plan or search if a similar feature has already been requested? ### Screenshots One of the possible could include returning the possible Reviewers in the format "Name (FullName)" like in the edited screenshot below. This would enable with the existing code searching for the FullName in addition to the username ![Image](https://github.com/user-attachments/assets/31896f79-9462-4d0b-b780-9ba3a9a4536c)

GiteaMirror added the type/proposal label 2025-11-02 11:12:55 -06:00

GiteaMirror closed this issue

2025-11-02 11:12:55 -06:00

GiteaMirror commented

2025-11-02 11:12:55 -06:00

@localleon commented on GitHub (May 2, 2025):

It seem's like there's an option ui.DEFAULT_SHOW_FULL_NAME = true to enable the behaviour we wnat. The UI then becomes the following (e.g. without any modifications from my side)

@localleon commented on GitHub (May 2, 2025): It seem's like there's an option `ui.DEFAULT_SHOW_FULL_NAME = true` to enable the behaviour we wnat. The UI then becomes the following (e.g. without any modifications from my side) ![Image](https://github.com/user-attachments/assets/43b643a2-bbdd-476c-9cf5-ed16dbe63638)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14436