Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra
Thanks everyone for the clarifications to this request. Upon further technical review, we have decided to decline this request at this time.
Please continue to contribute your ideas — they push us to innovate, problem solve, and really understand your needs.
If you're not going to do this then you REALLY need to solve the UI problem. People keep sending new messages when what they should be doing is replying to a thread.
The problem isn't threads or users. Its your UI that doesn't make it obvious what the right way to reply is.
I’d love to have teams on iOS and Mac notify me when an event is coming up.
It is recommended that you try adding the other SP pages as tabs within Teams.
If you feel this doesn’t meet your needs, please leave comments summarizing your usage scenario and why it doesn’t work.
Up-votes and all feedback is shared with the feature team on an ongoing basis.
Hi - I hope you see this. Seems like this has been closed for a year.
Teams Wiki is really good because it allows people to comment on things and it shows up in the team channel. It can spark conversation. The Sharepoint wiki does no such thing.
I'm fine if you keep them separate but at least allow web access to the wiki. Why is it ONLY available in the teams app/webapp? Just allow us to display the same thing as a page in a team Sharepoint too - its all HTML. Teams is an electron app anyway. Theres nothing fancy here.
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 isn't that hard. What is your intended interaction model here?
Is it mostly chat, with the option to make a thread? Then reply needs to be an action button in the corner of a message, not at the bottom taking up space. Chat needs compact messages nearly touching each other.
Is your intended model to be mostly threads? You're actually creating "posts" like on facebook then, not straight chat. The "new conversation" box should either be hidden behind a button ("create new conversation") or the reply box on each post should be exposed for typing into.
Pick a model. You're neither here nor there and it's making it even worse.
We have some channels that have the same name as the folder they should use. Like the "Project X" channel would also be the folder we store files for Project X.
Everything is nice and tidy except for the random collections of attachments uploaded in the channel that are stored at the top level. I want to be able to choose the subfolder (like "attachments" or something) so its not a mess.
Otherwise I need to pick different channel names and different project folder names on Sharepoint, which would make TWO top level folders called Project X Chat and Project X Files. Thats silly.
Clippy is flattered by all the attention but plans to continue his retirement.
I would very much prefer clippy over tbot. Like not even as a joke. it would be a great way to reimagine an old MS friend.
There was a lot of hate towards clippy, but I was young when he came around and he was actually helpful to me. Also he did tricks.
This. 100% this.
just want to say that I like the wiki more than one note. we don't use one note in my team, wiki is nicer. please dont remove it.
1 vote0 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →
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.
I could really use this right now
We are getting closer… the team is almost ready to rollout MacOS notification support internally for testing – we hope to have it to the public by the end of this quarter.
This isn't just about looking right. I put on "do not disturb" whenever I have a meeting and I need to share my screen. This disables all notifications.
That doesn't work for Teams and can potentially expose something very embarrassing while screensharing. Like someone making a comment about another person not thinking it might show up on a webconference.
Do not disturb is an important feature. Don't break it please.
The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.