You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behaviour:
If you search for a user in a participant search field and the participant is not in the participant-list then it is possible to run into one Error: Error: A user with the username <name> already exists
Reproduction:
create the account Firstname: xx, Surname xx; automatically will create username: xxxx
navigate into a meeting > motion > LoS
Search for a participant xxxx
you should get the option to "+ create User"
if you activate the option the Error is thrown: Error: A user with the username xxxx already exists
Wanted behaviour:
the input field: Select or search new speaker ... should send the whole string as the surname
If you have the input Kim Meier and create a new user, then the created account should have no first name and the surname Kim Meier
the User which is created should be inactive
after a user is created a snackbar should open which says: "A user with the Surname '' and the username '' was created"
The text was updated successfully, but these errors were encountered:
The createNewSelectedUser uses the userRepo.createFromString function.
A possible solution is to clean the parsed username in this function and use the backend generate code to set the username. As far as I know, this was the solution, we want to go for.
Current behaviour:
If you search for a user in a participant search field and the participant is not in the participant-list then it is possible to run into one Error:
Error: A user with the username <name> already exists
Reproduction:
Error: A user with the username xxxx already exists
Wanted behaviour:
Select or search new speaker ...
should send the whole string as the surnameIf you have the input
Kim Meier
and create a new user, then the created account should have no first name and the surnameKim Meier
The text was updated successfully, but these errors were encountered: