We have a similar use case.
We use Zapier to automate some processes across various apps and SaaS solutions.
We want to notify individual users through Teams in certain situations.
@mention provides a flexible way to notify the team or an individual within a specific context.
The notification is provided across all device access paths and persists.
This seems like it would be fairly straightforward to implement.
As mentioned in the prior status, the channel limit was raised from 100 to 200.
In the near future a retention limit will be set so you can still go back and reinstate a channel you had deleted. Once the retention period has expired then the channel will get a hard delete which will free up the space and no longer count toward the 200 channel limit.
This will help with some of the issues you have voiced in the comments below.
But I understand many of you wish the limit to be further increased. I will continue to provide your votes and comments to the feature team.
This feature is on the backlog. We’ll update when we have more details.
This request is now being reviewed by the feature team! I’ll keep you posted as to the future decision.
Item 1 and 2 are Under Review.
Item 3 has been Completed.
I’ll keep you posted as I hear more on this request.
This is a hot button for our organization. We'd like:
Make the tenant default: autocollapse off
Allow: users to collapse and uncollapse as they please, remembering state
Provide: UI/UX to collapse all, uncollapse all
We find the autocollapse of Team channels and the autocollapse of threads to be a real nuisance. I can't tell you how many times I've personally missed important messages because of autocollapse and the easy-to-overlook "See more..." link.
I'd much rather have the data always visible and have to scroll more or manage the collapsed sections on my own.
Please, for the love of productivity, don't auto-hide my content!
I really like the suggestion of creating an alarm on a message, so you come back to it. I’ve passed this on to our engineering team.
Meanwhile, here’s another feature you can utilize for the same purpose — use our “bookmark” button, which is in the upper right corner of every message. This will save that message or thread directly to your profile. To access your saved messages, just click your face in the upper left corner of the product. You’ll see a tab in the left rail that says “Saved.” This is like a list of little reminders.
Hope that helps! :-)
We are working on a better experience in Teams when a user is not connected to the internet. No timeline to share at this point, but we will keep you posted.
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.
So happy to share that this is off the backlog and we are actively working on it!
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
Would really like this feature. It could be a tenant setting, but I think most would choose to have threaded conversations in chats once they use Teams for any length of time.
A byproduct of the different interface in channel conversations vs chat conversations is users become accustomed to entering a message at the bottom of the screen for chat and forget to use "Reply" in channels, fracturing threads. We do user training regularly in attempt to prevent this.
We run into this request regularly. Group chats are a great catalyst for working together on a topic but it doesn't take long to need the full functionality of a channel in a Team. Features that you gain from becoming a channel include: findability - a group chat can't be found unless you're a member, SharePoint, email address, better long term data accessibility and more.
We lock down Team creation, so there might need to be a "request a conversion" process to allow someone with Team creation privilege to do the conversion.
This feature request is still working its way through the backlog queue.
14 votesSteve Minar shared this idea ·