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: Mark communication tab when you get a thread reply #9723

Open
JanaNF opened this issue Nov 10, 2024 · 0 comments
Open

Communication: Mark communication tab when you get a thread reply #9723

JanaNF opened this issue Nov 10, 2024 · 0 comments
Labels
communication Pull requests that affect the corresponding module feature programming Pull requests that affect the corresponding module text Pull requests that affect the corresponding module

Comments

@JanaNF
Copy link

JanaNF commented Nov 10, 2024

Is your feature request related to a problem?

Right now, I have to manually check my messages to see if I get a reply in a thread. Through that, I missed answers/follow-up questions, which is quite frustrating.

Describe the solution you'd like

It would be great if the communication tab (red point) and the chat (blue line + counter) were marked when you got a thread reply in a public/private/DM channel.

Describe alternatives you've considered

No response

Additional context

No response
@JanaNF JanaNF added the feature label Nov 10, 2024
@github-actions github-actions bot added communication Pull requests that affect the corresponding module programming Pull requests that affect the corresponding module text Pull requests that affect the corresponding module labels Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
communication Pull requests that affect the corresponding module feature programming Pull requests that affect the corresponding module text Pull requests that affect the corresponding module
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JanaNF