expand conversations default option
Add USER setting to expand all by default.
There's an existing idea for Collapsing/expanding conversations where it looks like they're working on implementing an Admin setting for collapse/expand, and a collapse/expand all button.
However, many of the comments on that idea are asking for something different:
Give us a USER-configurable option (not just admins) for whether threads are shown expanded or collapsed.
I feel like I spend most of my time catching up in Teams clicking "N replies from ..." or "See more" and would much prefer for everything to be shown by (my user-configured) default.
Even if this option was just for the "See more" behavior it would be WAY easier to view updates. Especially for channels we use for daily management, almost every reply is half-hidden with a "See More" link. I just scrolled through today's daily check-in thread which meant clicking EIGHT expander links, with scrolling in between.
CJ
shared this idea
103 comments
-
TJS
commented
Can you make it more like Slack? Teams takes up way too much screen real-estate for what it does. Adding bot integrations and auto-responses are really helpful for onboarding new team members. Auto-collapsing conversations and how Teams threads conversations within the same channel is the WORST!!! At minimum that UI needs a toggle in preferences to auto-expand conversations. The list goes on, but knowing how fantastic DevOp is, there should be hope for Teams to not be so... ******.
-
Anonymous
commented
yes, this auto-collapse is very very frustrating!!! We should be able to show full by default or user-selected preference, and have some easy ways of navigating conversations e.g. by a date scrollbar or something
-
Stephen
commented
Or replace conversations with the Yammer experience!
-
Al
commented
I've missed important conversations in the thread because it was collapsed by default. I need an "expand all" button and also a setting to make it expand all by default.
A variation to my request would be to have it remember across launchings the status of the collapse/expand method. Say I expanded a section; exited MS Teams, re-launched MS Teams, and find the expanded section still expanded as I left it.
-
Lisa M
commented
We were just forced to migrate to MS Teams in my org. We use the desktop version. Auto-collapse is INFURIATING! I'm missing important messages and spending way too much time trying to go back and find information in previous messages. PLEASE give users the option to auto-expand original messages and replies to conversations!
-
jrr
commented
PLEASE!!
STOP building everything for tablets and phones.
I know that MS does not build desktop computers anymore, but that's no reason to limit the functionality of those tens of millions of users who work on full sized computers every day.
-
Kevin J Dugan Jr
commented
The threaded view is very easy to miss updates. Can we get this to always be expanded?
-
Anonymous
commented
PLEASE! This collapsing threads issue has caused problems in our organization time and time again. It's VERY easy to miss the fact that a large thread has been collapsed and may require NUMEROUS clicks to fully unfurl. It has been the source of extra confusion and text chatter just to point out this collapsing behavior.
What you save in physical screen space is more than lost in time and extraneous texting of the form "Oh, I see -- I missed the whole conversation...".
-
Rikard Fröberg
commented
This is a deal-breaker for me. Other users in my org seem to accept this for reasons unknown to me. Another feature - perhaps worthy of a suggestion of its own - is copying a post from one channel to another (or to a private chat). Try creating a post with a few code-formatted blocks mixed with plain text. Now try to copy the whole post. I couldn't get this to work other than editing the original post, copying some plain text, editing the first code block, copying the text, create a new code block where I want to paste the whole post, and so on for each section of the post I simply wanted to copy.
If my org didn't force us to use Teams I would never ever consider using it for chatting.
-
Mel
commented
Agreed. We just switched to Teams and this does make it very difficult to see questions and answers in the replies.
-
Anonymous
commented
This absolutely needs to be an admin configurable option. Channel members can and will easily miss important information posted to the channel because they're not going bother with clicking on "see more" or "X replies" for everything posted.
-
kasa
commented
Any day now, right MS?
-
anon
commented
As you can see, it's like with Windows: when you are dominating the market, there's no need to develop the system.
-
Anonymous
commented
Because of the annoyance to having to click expand all the time to catch up on conversations, my team is considering switching back to using primarily email threads :( Please make this more usable
-
Kay Krüger-Barvels
commented
Yes, please. I have the exact same problem. A lot of individual clicks on "N replies from..." and "See more" are required to read what is happening in a thread. As a user, I want to be able to configure if replies should be expanded as default and how long a message is allowed to be before it is hidden behind "See more".
-
Anonymous
commented
This is ridiculous that this is not configurable. All other Communication tool (Slack, Glip, Mattermost) got it right the first time. Why is Microsoft always trying to reinvent the wheel (and sometimes making it square just to be different).
-
FranckS
commented
is this in the roadmap ?
-
FranckS
commented
Need this feature!!! our team is hesitant to migrate to teams because they don't have this feature!
-
ntay28
commented
As others have noted, this issue is making us consider sticking with Slack.
-
Pete
commented
Over 2 years on and this STILL isn't added?
WTF MS, this is a MAJOR pain point.
REMEMBER which conversations I have expanded/hidden and maintain that as I hop between channels/teams.
SUPER SIMPLE. JFC.
EDIT: Like most everything else about Teams coming from Slack, but this MIGHT keep us from migrating the whole company over (currently our team is evaluating it. Boss HATES this.)