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

Breakout rooms - numbering in breakout room name inconsistent #10533

Closed
thoemie opened this issue Dec 7, 2021 · 2 comments
Closed

Breakout rooms - numbering in breakout room name inconsistent #10533

thoemie opened this issue Dec 7, 2021 · 2 comments
Labels
wontfix Issue won't be fixed

Comments

@thoemie
Copy link

thoemie commented Dec 7, 2021

First of all, thanks to all people involved in making the breakout rooms possible!

Description:

A breakout-room has the breakout-room number in its name. When all breakout-rooms are deleted, and a new one is created, it is not named ".... #1", but instead the numbering continues from the previous breakout-rooms, e.g. it is called "Breakout-room #7".

Steps to reproduce:

  1. Start meeting as a moderator
  2. Create a breakout-room
  3. Observe the name: "Breakout-room # 1"
  4. Delete the breakout-room
  5. Create a breakout-room
  6. Observe the name: "Breakout-room # 2"

Expected behavior:

I would expect that the breakout-rooms be consistently numbered in the name, according to the number of current breakout-rooms. Or that the name of the breakout-room can be set by the user / changed interactively.

Actual behavior:

Breakout-room name has "wrong" number in the name and name can not be set or changed by user.

Server information:

  • Jitsi Meet version: jitsi-meet_1.0.5638 (latest release 2.0.6689)
  • Operating System: Ubuntu 20.04

Client information:

  • Browser / app version: Chromium Version 88.0.4324.150 (RPM Fusion Build) (64-bit)
  • Operating System: Fedora 32
@saghul
Copy link
Member

saghul commented Dec 7, 2021

This is currently a known issue. We'll make the name configurable in the UI in a future update.

@stale
Copy link

stale bot commented Apr 18, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Issue won't be fixed label Apr 18, 2022
@stale stale bot closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix Issue won't be fixed
Projects
None yet
Development

No branches or pull requests

2 participants