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.

Sign up for GitHub

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

Jump to bottom

Communication: Add sub-groups to communication channels. #9621

Open
Feras797 opened this issue Oct 28, 2024 · 1 comment
Open

Communication: Add sub-groups to communication channels. #9621

Feras797 opened this issue Oct 28, 2024 · 1 comment
Assignees
@asliayk
Labels
communication Pull requests that affect the corresponding module core Pull requests that affect the corresponding module exam Pull requests that affect the corresponding module feature lecture Pull requests that affect the corresponding module programming Pull requests that affect the corresponding module text Pull requests that affect the corresponding module

Comments

@Feras797
Copy link

Is your feature request related to a problem?

In this course the amount of sub-channels will grow and it will be annoying to scroll to the current one after some time:
image

Describe the solution you'd like

It would be nice to have a sub-group/folder in which the channels are stored. E.g. for above example: "Past" and "Current", where both can be expanded.

Describe alternatives you've considered

keeping the current system works as well, but channels can get very convoluted over time.

Additional context

No response
@github-actions github-actions bot added communication Pull requests that affect the corresponding module core Pull requests that affect the corresponding module exam Pull requests that affect the corresponding module lecture Pull requests that affect the corresponding module programming Pull requests that affect the corresponding module text Pull requests that affect the corresponding module labels Oct 28, 2024
@krusche
Copy link
Member

krusche commented Oct 28, 2024

Good suggestion, we can definitely take the due date into account.
A workaround is to hide channels that are not interesting to you any more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asliayk asliayk

Labels
communication Pull requests that affect the corresponding module core Pull requests that affect the corresponding module exam Pull requests that affect the corresponding module feature lecture Pull requests that affect the corresponding module programming Pull requests that affect the corresponding module text Pull requests that affect the corresponding module
Projects
Communication Webclient
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@krusche @asliayk @Feras797