We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.Michael van der Haven commented
I'd argue it would be an easy thing to resolve. Products like Yammer (also Microsoft owned) and Facebook are the day-2-day tools many people use and they never have that problem.
So, take a look at how it is implemented in those products and copy it (copying the experience from Yammer would simply be learning from your own company, right?)
Also: if there is an accidental reply, a merge threads or just deleting the conversation option would be nice as well (other suggestion I guess)
The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.
Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.
Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.
The feature team is still considering this item. No confirmation yet.
This request is still on the backlog.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
~AlexMichael van der Haven commented
Work-arounds are probably not what we're waiting for. I'm used to the option in Slack, and given the organization I'm currently in where reorganizations and relocations of sub-teams (with their own channel, where I hate the fact that private channels are not available as well), moving a channel from one-team to the other is a must.
A work-around would be to copy the complete conversation stack in the channel, but then we lose the meta-data. (and in all honesty: from a compliance perspective this simply needs to be available)
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
As stated in the last update, the ability to use multiple Teams accounts at the same time is being implemented in stages for Desktop. Faster tenant switching functionality on the Windows client has been rolled out to the public ring fully, and Mac will begin rolling out soon. Work is in progress on cross-tenant notification improvements, and support for multiple accounts on desktop will follow. We’ll keep you posted!
Note: The ability to use multiple Teams accounts at the same time is supported on iOS & Android today.
Alex & the Teams team
We are still considering this feature for future releases, and will continue to update the status when it changes.
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.