Make issue/PR assignees and reviewers search by real name #14

Closed
opened 2023-02-08 14:38:16 +01:00 by Sergey Sharybin · 6 comments

Currently the assignees and reviewers fields are limited to search by a user name, and does not consider the real user name. This makes it very hard to find people when you knwo person's name and don't know their nickname.

This works differently when you filter using the @ in the comment box which searches and visualzied both real and user name.

Currently the assignees and reviewers fields are limited to search by a user name, and does not consider the real user name. This makes it very hard to find people when you knwo person's name and don't know their nickname. This works differently when you filter using the `@` in the comment box which searches and visualzied both real and user name.
Sergey Sharybin added the
gitea feature request
label 2023-02-08 14:38:16 +01:00

Hi, I am trying to add this feature, and I found that in your custom/conf/app.ini file, if the flag DEFAULT_SHOW_FULL_NAME is set to true( reference to example configuration: app.example.ini ), then assignees and reviewers fields will become seached by fullname. I am not sure if this customization meets your requiment, or do you need both username and fullname to show, no matter what DEFAULT_SHOW_FULL_NAME flag is.

Hi, I am trying to add this feature, and I found that in your `custom/conf/app.ini` file, if the flag `DEFAULT_SHOW_FULL_NAME` is set to true( reference to example configuration: [`app.example.ini`](https://github.com/go-gitea/gitea/blob/757b4c17e900f1d11a81bc9467d90e6c245ee8f2/custom/conf/app.example.ini#L1238) ), then assignees and reviewers fields will become seached by fullname. I am not sure if this customization meets your requiment, or do you need both username and fullname to show, no matter what `DEFAULT_SHOW_FULL_NAME` flag is.
Author
Owner

This option is probably indeed something we should consider using, even regardless of the assignees search.

@hestergong, am I right that when this option is enabled the assignees can only be looked up by real name when it is set?

This option is probably indeed something we should consider using, even regardless of the assignees search. @hestergong, am I right that when this option is enabled the assignees can only be looked up by real name when it is set?

This option is probably indeed something we should consider using, even regardless of the assignees search.

@hestergong, am I right that when this option is enabled the assignees can only be looked up by real name when it is set?

Yes, if it is enabled, the search results in assignees and reviewers will only have realname, but not username.
We could add a feature that allows to search both username and realname no matter the option is enabled or not if the current behavior is not enough for your usage. @Sergey

> This option is probably indeed something we should consider using, even regardless of the assignees search. > > @hestergong, am I right that when this option is enabled the assignees can only be looked up by real name when it is set? Yes, if it is enabled, the search results in assignees and reviewers will only have realname, but not username. We could add a feature that allows to search both username and realname no matter the option is enabled or not if the current behavior is not enough for your usage. @Sergey
Hi, please check this PR: https://github.com/go-gitea/gitea/pull/23463
Brecht Van Lommel added the
deployment
label 2023-03-20 14:25:03 +01:00

So this landed in Gitea main now, thanks!

I enabled DEFAULT_SHOW_FULL_NAME and merged main into the blender-merged develop branch. It's now waiting for the next time we rebuild and restart Gitea to start working.

So this landed in Gitea main now, thanks! I enabled `DEFAULT_SHOW_FULL_NAME` and merged `main` into the `blender-merged develop` branch. It's now waiting for the next time we rebuild and restart Gitea to start working.

This was deployed now.

This was deployed now.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-projects-platform#14
No description provided.