Incredible that this wasn't rolled out with the platform. Very short-sighted.
This absolutely needs to be addressed. I've brought it up in other threads here that related to the reply button.
The 100+ employee org I maintain right now has a massive problem with accidentally creating a new convo instead of replying - heck, even i do it sometimes. Every other threaded convo system i'm aware of utilizes a "Create a new post" kind of button and that seems to be a universal standard that works very well.
This suggestion is hilarious and totally worthy of serious consideration. I’ll pass this to our design group!
Thanks for helping us make Teams awesome. :-)
YES YES YES!!!!!
Send me a tweet at @skprufo if you have any questions on this. I’ll let you know when it goes live.
I know this is a common request. Please keep voting this up if this is a major pain point for you. We have it in planning but your votes will help accelerate when work starts. Every vote counts!
Can't move my entire dev/product team over until an import function is created.
**** - even a third party "so-so" bandaid would be good enough.
Thank you for this feedback!
You’re right, Sam: the only difference between these two tabs are their privacy settings. They have the same function: chatting.
While we may not implement the solution above, we hear the feedback loud and clear and are reviewing the problem.
Thank you for your feedback and please continue to help us make Teams great!
I like Manny's idea below.
This is a preference based issue and should be "fixed" so that both sides win.
After reading a few of the "use cases" below - it seems the folks that are requesting the merger of "Chat" and "Teams" are ones working in small groups/companies.
For an org of our size - having these tabs combined would destroy functionality. Maybe it would be better to provide users (or admin) with the ability to pick between two "types" of views for Teams. One of these views could be better situated for those who only have a handful of people in their team.
We very much enjoy having the "peer to peer" chat functions (those from S4B) under a separate section.
If the "Teams" and "Chat" tabs were to be merged together, it would be a chaotic mess!
Allow admins to decide which style UI that works for their environment - forcing this kind of change down the pipe on us will absolutely move us away from Teams entirely.
We’re working on a way to make the Reply button drive you a little less bonkers. :-)
If you are interested in testing this feature, please sign up here:
As always, THANK YOU for helping us make Teams awesome!
This seems insane to me.
If the reply button is made LESS pronounced then every channel will turn into a messy chat room with no organization!
I can understand how this request might have been generated from some small 5-person crew but with an org of 100+ people like ours, a less obvious way to "reply" will destroy functionality.
I believe there should be a button at the bottom for "Create a new post/convo" (as any threaded conversation platform has?) and the reply field can happen when you click on a convo - removing the wasted space and complaining from smaller groups.
The threaded conversations work great but I'd vote that the "reply" button needs to be completely rethought.
My users still (regardless of the multiple trainings) reply to conversations by creating their own topic because the "reply" button isn't intuitive.
Something needs to be reworked so that the layout drives a user toward correctly replying to a conversation.
I believe creating a button at the bottom that says "Create topic" which then allows users to enter text into the field would work much better and drive users to utilize the platform correctly.
This gained a lot of traction five months ago and seems to have tappered off. Now that we’ve created “Follow a channel” — do you still have a business need for this feature? If so, could you share that information in the thread here on UserVoice, under this item.
I have dropped S4B and migrated comepletely over to Teams in our org (100+ employees).
I get alot of complaints from users who want to be able to "mute" particular channels that may/may not apply to them. Currently you can only turn off notifications globally which is not effective.
Many of our users have turned off notifications entirely because they have no way to control which channels alert them - this is killing the adoption of the platform because now no one sees anything going on.
Thanks everyone, I’ve sent your feedback over to the Framework team. They are working on a solution. Will let you know as this progresses.
I know its been a little quiet on UserVoice and in our release notes lately, and I can tell you why. We’re thoroughly going through user feedback to prioritize our work and solve the problems you’re reporting. In this effort, we’re bringing you this feature! Its planned and I’ll update once work is underway.
Thank you again for contributing your voice, votes and enthusiasm for Teams. We’re listening, even if sometimes we’re quiet. (Oh, I also took a small vacation! :-))
P.S. I’ll be providing more user updates via our new Teams blog! Check it out here: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/bg-p/MicrosoftTeamsBlog
A must have!
Start off your weekend with good news: we’re working on this!
Thanks to everyone who brought this feature to the forefront and shared feedback on their use case scenario. Very helpful!
I wrote some more product updates on today’s Teams blog in my weekly column, “Weekend Reading” —
"What is more important to you, having the presence be different (i.e. reflect your machine activity and not just your Teams activity) or having it be synchronous to Skype for Business?"
-- If Teams based it's presence off of machine activity then by nature it would be synchronized to S4B. Teams should be capable of being the only in house chat platform in an org. Those who have both only seem to do so because of the missing features that are slowly being implemented.
Why are you using Skype for Business and Teams at the same time? (I’m not being facetious, this is an actual user research question so I can understand your use case/scenario.)
--I've migrated all users off of Skype and over to Teams. There are alot of complaints currently with screen sharing, presence settings, and some other S4B features that aren't present - however this platform is fine for our 100+ employee organization.
I've successfully removed S4B from our environment and migrated all users to Teams (100+ employees)...
Unfortunately, they are all very frustrated with the "presence" functionality.
Why can't Team's presence system work the same way S4B did?
-Presence system is based on computer usage (not app usage)
-Presence system is integrated to outlook (scheduled meetings turn user to "busy" - etc)
I'll bet if these simple features were built into Teams - no one would complain about it.
You had a great system before - zero sense in changing it!
But an issue that MUST be addressed none-the-less
Adding a +1 on this.
We've moved our entire org over from S4B to Teams and this has become a huge pain point.
If someone creates a group and some users decide they don't want to be apart of it - there is no escape and they are constantly hit with notifications on something they don't want/need.
I can understand this being a missed item at launch but for it to still continue being an issue is crazy. This is a MUST HAVE and needs to be correctly immediately.
This is under review! If you have more ideas/feedback specifically on this item, please sign up for user testing here: https://1drv.ms/xs/s!AryUNzh1ogZzif8pDcOcx2pW45I87w
You can also tweet me at @skprufo if you have any questions.
I've moved our entire org over to Teams and disable Skype across the board.
There is no reason I can find for our environment (or any other environment) to need both if Teams can provide some of the core features provided by S4B.
-Screensharing needs to not require a video/phone call
-Presence integration into outlook is a MUST
-Presence system based on device usage NOT app usage is a must
If we can get those things in place - 95% of my user complaints will be solved and our environment will no longer have a use for S4B
You may have already heard this because we announced this date at our public release of Teams last month, but I thought I’d email everyone just in case they didn’t get the news. We’ve publicly committed to a date for this feature, and it is June!
Its a difficult feature to pull off, and we want to make sure to get it right for you. Thank you for your patience and most of all, thank you for bringing this idea for us! We’re excited to soon be able to mark the #1 UserVoice item as complete. :-)
VERY unhappy to find out that I was unable to allow my users to share files within their groups externally. I assumed this would be more of an internal tool by nature but allowing external parties in to an extent is a MUST if I have any hope of migrating our users away from Slack.
The desktop screenshare is an important feature of skype that my users utilized often.
Forcing users to do a video conference first before being able to share their screen is a huge inconvenience. Either allow users to set a preference so that their webcam is not defaulted on during a video call or provide a way to share a screen outside of a video call.
Hi everyone, thanks for the additional comments after I marked this as “completed.”
I’ve looked through the comments and elevated this to the dev team. They have informed me they are working on this and are starting testing now. So, presence will soon be more active to your machine activity and not just your Teams activity.
Thank you for keeping this ticket alive so we can truly “complete” this issue!
This is insane.
Skype for Business/Lync did it right. It showed if the user was available or away (literally).
This "update" to Teams now automatically switches you away but requires manual intervention in order to be shown as available?! Whoever made this decision needs to stop providing input.