github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-05 19:18:16 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Partially search users by name #654

New Issue
Closed
opened 2025-11-01 21:01:15 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 21:01:15 -05:00
Owner
Copy Link

Originally created by @GrahamJenkins on GitHub (Oct 3, 2025).

Description

When adding users to teams or projects, the search requires an exact (case insensitive) match before any results appear. The expected behavior is to use an ilike 'search' query so that any (partial) string is searched against email/usernames.

Also, search should only trigger when search.length > 0.

Which alternatives did you consider using instead?

I was looking to see if there was an admin panel or something that would list all registered users, then I could find their exact username/email, but that doesn't seem to be an option.

As it stands, the default settings (ie without specifying an environment variable I wasn't aware of) make new users invisible to search by email or username. There is no user list I can find, and all instances of user search I can find require exact email/username matching. I would argue that this puts excessive burden on the end user to A know who has an account on the system, and B know (and type) their exact username/email address.

Thanks for the consideration! I just installed this yesterday and have been testing all functionality. Looks pretty good so far!

Originally created by @GrahamJenkins on GitHub (Oct 3, 2025). ### Description When adding users to teams or projects, the search requires an exact (case insensitive) match before any results appear. The expected behavior is to use an ilike '*search*' query so that any (partial) string is searched against email/usernames. Also, search should only trigger when search.length > 0. ### Which alternatives did you consider using instead? I was looking to see if there was an admin panel or something that would list all registered users, then I could find their exact username/email, but that doesn't seem to be an option. As it stands, the default settings (ie without specifying an environment variable I wasn't aware of) make new users invisible to search by email or username. There is no user list I can find, and all instances of user search I can find require *exact* email/username matching. I would argue that this puts excessive burden on the end user to A know who has an account on the system, and B know (and type) their exact username/email address. Thanks for the consideration! I just installed this yesterday and have been testing all functionality. Looks pretty good so far!
GiteaMirror commented 2025-11-01 21:01:16 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 6, 2025):

The problem here is that such a feature would allow enumerating all user accounts on an instance. Not a big deal for internal use, but a no-go on public instances. That's why it is a user configurable option.

If you search for users to assign them to a task, it will match partial instances of the username/name as well, but you need to have the project shared with the user first.

There is a config option for the default user setting: https://vikunja.io/docs/config-options/#1-defaultsettings-discoverable_by_name

@kolaente commented on GitHub (Oct 6, 2025): The problem here is that such a feature would allow enumerating all user accounts on an instance. Not a big deal for internal use, but a no-go on public instances. That's why it is a user configurable option. If you search for users to assign them to a task, it will match partial instances of the username/name as well, but you need to have the project shared with the user first. There is a config option for the default user setting: https://vikunja.io/docs/config-options/#1-defaultsettings-discoverable_by_name
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#654
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?