This suggestion is still planned. I don’t have further updates on timing, but will share as we have them. Thanks.
I stop in from time to time to see if Teams is getting anywhere and I can't say I'm surprised to find that it hasn't.
To anyone reading this, if you aren't dependent on Microsoft Teams, I recommend switching to Slack, Discord, or some other competing service. Teams tries too hard to be "cute" instead of focusing on actual basic features that help with productivity and until Microsoft figures that out you'll just be wasting your time using it.
Beating a dead horse here, but if any of you can switch to Slack then you should do it. It's clear that Teams is being presented as a messaging system for cute optics instead of actual productivity.
After using Teams for over 7 months, my team switched to Slack last week. We won't be coming back. The lack of development on highly requested features such as this leads me to believe that Teams will never be a proper competitor in the Slack/Discord space.
So I just saw that this request is not being done: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16925779-hide-the-reply-button-under-every-message
How are we supposed to get a truly compact layout when half the problem is the bloated mess that threading makes?
I appreciate that changes are being made, but this change is barely even noteworthy. The chat is the problem and the only noticable change there is that short text no longer gets randomly split into two lines. In the end, I still only see 7-8 messages in a maximized window.
DENSITY! I should be able to see more than 7 single line messages in a maximized 1080p window. Like, far more than 7. Like... 40-50 single line messages. Like IRC. The current design caters too hard to this weird "teehee! I'm at work to have fun! I can post memes and pretend I'm having casual facebook conversations with chat bubbles!" vibe. Leave the "fun" tool designs to phones/tablets/non-work software.
This sounds like a great idea. Maybe the Teams team will get it through their heads and properly implement these threaded conversations correctly along with implementing a proper separate group chatroom function.
So happy to share that this is off the backlog and we are actively working on it!
Remember, everyone: Read receipts only prove that a message was displayed on a screen. It does not prove that the user actually read the message or acknowledged its existence. This is true in every chat app and email as well. I understand some usage for this, but if you have "mission critical" things that depend on this feature then you might want to consider requiring your users to actually respond.
"Read receipts" is such a misnomer. It doesn't prove that the message was read, let alone understood or acknowledged. It means it was open on their screen for a fraction of a second. No one in their right mind should actually be using that feature(on Teams, Facebook, iMessage, email, anywhere) as confirmation that a message was read.
@Gordon Are you telling me that if someone @mention's you in a thread, you continue to get notifications for all responses to that? That's awful!
I'm curious, what would this actually do? You've already received whatever notifications came from it since that's probably the only reason you know you were @mentioned. What would unmentioning actually help?
Switched to Slack. This is an annoying bug that should have been fixed by now.
I would like to add that, for me, this only happens after the Conversations view has several(100+) individual conversations loaded. It won't occur on a fresh launch of the program. However, the more messages that get loaded, the farther you get scrolled up when the bug hits.
Sorry everyone, but the feature team has decided to decline this feature request.
Can the feature team explain why something as basic as customizing the font is not possible?
Thank you for your suggestion! We really appreciate the feedback and idea. We have reviewed this request and started working on it. I’ll let you know as it nears completion.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
This is a great idea if they ever separate out the chatroom-like feature from Conversations. My Team uses the conversations section like a chatroom, hiding the "start a new conversation" box would just make the workflow of this app even worse for us.
55 votesunder review · 5 comments · Public » IT Pro - Security and Compliance · Flag idea as inappropriate… · Admin →
This seems completely antithetical to the point of having a "Team". If you're discussing something that the rest of the Team shouldn't see, then you should be making a separate Team or just messaging them in private.
Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.
As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”
Well, that's entirely unacceptable.
The reply button being too big is just a symptom of a larger problem. There's no way to force a "conversation" to be exactly like every other chatroom in existence: A chronological, single-threaded set of messages.
I honestly don't understand how anyone finds this "it's a chatroom, but it's also like a message board system" system useful. Clearly some people responding to this bug enjoy that feature, but it should absolutely be something that can be turned off, or split off into its own message-board style feature for people who want to respond chronologically out of order to things. My coworkers and I do not use this reply feature at all and do not plan to. A maximized window on a 1080 screen can fit a whopping 7(!) single line messages on the screen at once. That's absolutely terrible when coming from Discord, Skype, or IRC.
The reply button is the most confusing thing about these "chat rooms". There needs to be an option for this to be an actual single threaded chatroom and not some bizarre hybrid chatroom/message board feature.
This feature request has now moved to “working on it”. The team is actively working on this request and I will share more details as they become available.
Absolutely agree with #2 and everything in general. For Microsoft to claim that Teams has "chat history" is them being disingenuous. Yeah, there's a chat history, it's just barely functional. Being unable to jump to the message in the search results is literally the worst part of Teams.