Case Insensitivity When Searching for Assignees #18

Closed
opened 2026-02-27 14:49:37 -05:00 by deekerman · 2 comments
Owner

Originally created by @DieGurke on GitHub (Oct 13, 2021).

Currently the exact user name has to be typed into the assign user field.
It would be much more intuitive and beneficial for the workflow, if this field was case insensitive.

Originally created by @DieGurke on GitHub (Oct 13, 2021). Currently the exact user name has to be typed into the assign user field. It would be much more intuitive and beneficial for the workflow, if this field was case insensitive.
deekerman 2026-02-27 14:49:37 -05:00
Author
Owner

@kolaente commented on GitHub (Oct 13, 2021):

This actually depends on the db you're using. I'm assuming you're using postgres? mysql and sqlite do this by default.

Makes sense to have this though. Do you want to send a PR?

@kolaente commented on GitHub (Oct 13, 2021): This actually depends on the db you're using. I'm assuming you're using postgres? mysql and sqlite do this by default. Makes sense to have this though. Do you want to send a PR?
Author
Owner

@kolaente commented on GitHub (Oct 1, 2022):

Fixed in github.com/go-vikunja/api@c076f73a87 - please check with the next unstable build if the problem went away.

@kolaente commented on GitHub (Oct 1, 2022): Fixed in https://github.com/go-vikunja/api/commit/c076f73a87bc9b39b17389e25d0186ab71aa24bf - please check with the next unstable build if the problem went away.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
starred/vikunja-go-vikunja#18
No description provided.