Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meeting > User create: issue with present status during user creation #4419

Closed
MSoeb opened this issue Nov 27, 2024 · 1 comment · Fixed by #4475
Closed

Meeting > User create: issue with present status during user creation #4419

MSoeb opened this issue Nov 27, 2024 · 1 comment · Fixed by #4475
Assignees
Labels
Milestone

Comments

@MSoeb
Copy link

MSoeb commented Nov 27, 2024

Describe the bug
If you add a user to a meeting or create a new one, the presence status is always set to absent. It does not matter whether the presence checkbox was checked in step 3 or not.

When debugging with Loki, we noticed that the attendance is not sent when referencing. See picture.
image

Something is sent during the new creation, but this has no influence on the presence status. See image.
image

How to Reproduce
Steps to reproduce the behavior:

  1. open a meeting
  2. open participants
  3. create a new user. uncheck and check presence state during creation. > check presence state after creation.
  4. Add a new user by referencing an existing user. presence checkbox should stay marked -> after creation the user is not present

Expected behavior

  1. when creating or referencing users in a meeting, the presence checkbox should not be checked by default.
  2. if the presence checkbox is checked, the user should be created as present.
@MSoeb MSoeb added the bug label Nov 27, 2024
@MSoeb MSoeb added this to the 4.2 milestone Nov 27, 2024
@reiterl
Copy link
Member

reiterl commented Nov 29, 2024

I can reproduce it. I have looked into the code. It seems that presence set mechanism is not in participant-controller in the create method. Hmm...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants