We’re fixing bugs identified in the comments, and other user reports we’ve received around markdown, but we’ve decided we’re not going to fundamentally change our markdown support.
This is the first time we’ve declined a request, and it didn’t come easily. We weighed this against other important features we’re working on to deliver and we had to make some tough choices.
Really appreciate your understanding on this, and please feel free to ping me if you have any questions, complaints, or need to rant.
Syntax highlighting! What the **** Teams devs?
This suggestion is still planned. I don’t have further updates on timing, but will share as we have them. Thanks.Anonymous commented
Suphatra, the survey link doesn't work!
Why don't you guys: display the name and time to the left of the message rather than at the top. Try to use as little vertical space as possible. Then smaller padding.
I’m switching the status to Partially Done.
The request for a Preview Team is still in the works. No new information is available at this time.
Team Discoverability is still being worked upon, no details are available at this time. If you support this idea please navigate over to the main topic and vote for it! https://microsoftteams.uservoice.com/forums/555103/
Change Prompt: this has been completed
831 votes173 comments · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →
The zoom feature has released to the public ring. Using CRTL + or CTRL – zoom in and out on a Windows PC.
I need to correct the information I provided last month about MAC. It appears the MAC version is still in testing and hasn’t yet gone out to the public. It is “In Testing” but will be coming to the public soon!
The item tracking this specific update can be found at: https://microsoftteams.uservoice.com/admin/v3/suggestions/16933183/activity
There now is a UI element that tells you your current zoom level and a Setting within the UI to preset your zoom preference.
Since the zoom feature could very well cover the vast majority of user needs, based on the majority of comments and feedback, I will flag this item as Partially Done.
Thank you for all the feedback and support!
Due to a priority shift we need to move this one onto the backlog again.
I’ll keep you posted once we can pick up the forward momentum again.
This request has been declined by the feature team.
Private channels may help with items such as this request once they are released. The Private channel topic is tracked at http://microsoftteams.uservoice.com/forums/555103/suggestions/16911079
Please note the handling of “Guest Accounts” is a separate ask and can be found at: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16911109-guest-access
The request about “Guest Access at the Channel” level is being tracked by this request: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31374577-guest-access-should-be-implemented-at-the-channel
Thank you all for the feedback.
Unfortunately due to re-prioritization this item has slipped back onto the “backlog” for the time being.
I hope to see it move back into “working on it” soon and will continue to engage the feature team with your feedback.
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.
Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.
As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”
The feature is still being worked upon. Many different changes are going into Teams and will provide a slow but steady pace to our performance increases.
I don’t have any new details at the moment but hope to get some additional feedback in the next several weeks.
This is still under review by the feature team.
The slash command changes are still in the works. I hope to have more details to share soon.
This request is still on the backlog.
Hi Everyone – thank you for your patience. As was commented by someone below, Suphatra is no longer at Microsoft, but rest assured we are working on this feature.