When assigning new users, I can currently only select by E-Mail.
It would be good if I can filter by both mail and name, and the name is displayed in the suggestions.
When assigning new users, I can currently only select by E-Mail.
It would be good if I can filter by both mail and name, and the name is displayed in the suggestions.
Looks like the settings were only taken into account when searching globally for users, not when searching for users with access to a list.
Fixed in 382a7884be - please check with the next unstable build if the problem went away.
Looks like the settings were only taken into account when searching globally for users, not when searching for users with access to a list.
Fixed in https://kolaente.dev/vikunja/api/commit/382a7884be1f37da5c8f657c4b17316d8691dd59 - please check with the next unstable build if the problem went away.
yes, it works now on 0.18.1+2040-9bbaa67eec but still two issues:
the display name should be shown in the autocompletion box (ideally plus avatar), not the email
the search should be case-insensitive
yes, it works now on `0.18.1+2040-9bbaa67eec` but still two issues:
- the display name should be shown in the autocompletion box (ideally plus avatar), not the email
- the search should be case-insensitive
The display name is now shown in the autocomplete box since 65fd2f14a0.
Case-insensitive search is another topic and depends on the database used (with mariadb and sqlite the search is already case-insensitive). A seperate backlog item exists for that.
The display name is now shown in the autocomplete box since https://kolaente.dev/vikunja/frontend/commit/65fd2f14a067ea9d79b352af00f3c316be883fdf.
Case-insensitive search is another topic and depends on the database used (with mariadb and sqlite the search is already case-insensitive). A seperate backlog item exists for that.
Thank you :)
We use postgres for scalability, and the case-insensitive search would be a great feature to always have :)
And you should also be able to search by username/e-mail, not just displayname.
Woops sorry, that option exists, but we really need the ability to make it default, could be simply an instance-wide config option.
And don't forget to make new releases ;)
Thank you :)
We use postgres for scalability, and the case-insensitive search would be a great feature to always have :)
~~And you should also be able to search by username/e-mail, not just displayname.~~
Woops sorry, that option exists, but we really need the ability to make it default, could be simply an instance-wide config option.
And don't forget to make new releases ;)
And you should also be able to search by username/e-mail, not just displayname.
But that already works? Displayname and email depend on a setting of the individual users though.
> And you should also be able to search by username/e-mail, not just displayname.
But that already works? Displayname and email depend on a setting of the individual users though.
Furthermore, a (potentially trimmed) list of all available people (including avatars, idk if that is supposed to work already?) should be shown when clicking into the assignee field, like in Wekan.
I corrected myself, you were too quick ;)
Furthermore, a (potentially trimmed) list of all available people (including avatars, idk if that is supposed to work already?) should be shown when clicking into the assignee field, like in Wekan.
Furthermore it would be handy to be able assign users by email and displayname via Quick Add Magic - for the email even without the domain if that is unambiguous (would be perfect for our case, as every user signs in with his company mail and the mail-schema is well known - so if the mail is test@domain.com mentioning @test should assign that user)
Furthermore it would be handy to be able assign users by email and displayname via Quick Add Magic - for the email even without the domain if that is unambiguous (would be perfect for our case, as every user signs in with his company mail and the mail-schema is well known - so if the mail is `test@domain.com` mentioning `@test` should assign that user)
Case-insensitive matching is a requirement here, assigning people is still quite janky.
And finding someone by e-mail-address still does not work, only if I enter the full address which is cumbersome :/
Case-insensitive matching is a requirement here, assigning people is still quite janky.
And finding someone by e-mail-address still does not work, only if I enter the full address which is cumbersome :/
Case-insensitive matching was implemented in the meantime. Searching for users via email is designed to only work with the full email address to avoid searching for "@" and getting a list of all users on an instance. I think it should be fine to lax this when searching for assignees as these are usually already known since they were added to a team or explicitely to the list already.
Case-insensitive matching was implemented in the meantime. Searching for users via email is designed to only work with the full email address to avoid searching for "@" and getting a list of all users on an instance. I think it should be fine to lax this when searching for assignees as these are usually already known since they were added to a team or explicitely to the list already.
just tested in try - it seems the name matches case-insensitively, but I have to enter the full name - there is no autocompletion:
e.g. when selecting a task, clicking assign user and typing "de" there is no suggestion
just tested in try - it seems the name matches case-insensitively, but I have to enter the full name - there is no autocompletion:
e.g. when selecting a task, clicking assign user and typing "de" there is no suggestion
When assigning new users, I can currently only select by E-Mail.
It would be good if I can filter by both mail and name, and the name is displayed in the suggestions.
That's already implemented. Users need to explicitely enable it in their settings though:
Nope, I have that Checkbox enabled and it still does not work, at least on unstable.
Reproduced on try.
Looks like the settings were only taken into account when searching globally for users, not when searching for users with access to a list.
Fixed in
382a7884be
- please check with the next unstable build if the problem went away.yes, it works now on
0.18.1+2040-9bbaa67eec
but still two issues:The display name is now shown in the autocomplete box since
65fd2f14a0
.Case-insensitive search is another topic and depends on the database used (with mariadb and sqlite the search is already case-insensitive). A seperate backlog item exists for that.
Thank you :)
We use postgres for scalability, and the case-insensitive search would be a great feature to always have :)
And you should also be able to search by username/e-mail, not just displayname.Woops sorry, that option exists, but we really need the ability to make it default, could be simply an instance-wide config option.
And don't forget to make new releases ;)
Assign users by displaynameto Assign users case-insensitively by displayname, username and email 5 months agoBut that already works? Displayname and email depend on a setting of the individual users though.
I corrected myself, you were too quick ;)
Furthermore, a (potentially trimmed) list of all available people (including avatars, idk if that is supposed to work already?) should be shown when clicking into the assignee field, like in Wekan.
Furthermore it would be handy to be able assign users by email and displayname via Quick Add Magic - for the email even without the domain if that is unambiguous (would be perfect for our case, as every user signs in with his company mail and the mail-schema is well known - so if the mail is
test@domain.com
mentioning@test
should assign that user)Case-insensitive matching is a requirement here, assigning people is still quite janky.
And finding someone by e-mail-address still does not work, only if I enter the full address which is cumbersome :/
Case-insensitive matching was implemented in the meantime. Searching for users via email is designed to only work with the full email address to avoid searching for "@" and getting a list of all users on an instance. I think it should be fine to lax this when searching for assignees as these are usually already known since they were added to a team or explicitely to the list already.
just tested in try - it seems the name matches case-insensitively, but I have to enter the full name - there is no autocompletion:
e.g. when selecting a task, clicking assign user and typing "de" there is no suggestion