Jerry Jackson
My feedback
-
13 votes
An error occurred while saving the comment -
17 votesJerry Jackson
supported this idea
·
-
1,817 votes
The ability to delete Bot messages feature has been added to the backlog. Thank you for your feedback!
An error occurred while saving the comment Jerry Jackson
commented
My last employer was using MS Teams (years ago when I voted for this functionality), my current employer uses Slack. I can't believe such a basic feature like deleting a message when you're the admin still hasn't been implemented THREE YEARS after it was requested. Honestly, even free slack is better than MS Teams.
Jerry Jackson
supported this idea
·
-
44 votes
An error occurred while saving the comment Jerry Jackson
commented
Existing ticket for this already.
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31019839-cache-something-anything -
265 votesJerry Jackson
supported this idea
·
An error occurred while saving the comment Jerry Jackson
commented
**** Edit (I had some typos which made my previous message not make sense. Also added new paragraph)
I hate how the link previews work. 90% of the links sent in our MS Teams is for atlassian products, so they all get the useless "Login to Jira..." link preview. I would really like to be able disable all link previews for atlassian products.
An even better option would be to allow us to login to teams with OUR atlassian login, so the generated links actually have the correct meta data. This would assume that link generation is happening on the senders Teams instance, and then sending the meta data as part of the message, or perhaps the receiver can login with their credentials so page metadata is scraped on the receivers end.
I doubt MS supports it anymore, but about 10 years ago in one of my C# applications I had an internet frame, which just used IE to render, but it also had access to your IE cookies etc. So if you had logged into a site in IE, you would be logged in the frame in my app too. Something like this would be useful here too. If MS Teams used the cookies/credentials from IE/Edge, it could actually generate useful link previews.
An error occurred while saving the comment Jerry Jackson
commented
I hate how the link previews work. 90% of the links sent in our MS Teams is for atlassian products, so they all get the useless "Login to Jira..." link preview. I would really like to be able disable all link previews for atlassian products.
An even better option would be to allow us to login to teams with out atlassian login, so the generated links actually have the correct meta data. This would assume that link generation is happening on the senders Teams instance, and then sending the meta data as part of the message.
-
69 votesJerry Jackson
supported this idea
·
-
51 votesJerry Jackson
shared this idea
·
-
31 votes
An error occurred while saving the comment Jerry Jackson
commented
This would be a very useful addition.
Related/Duplicated post:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32706418-mark-content-as-spoilerJerry Jackson
supported this idea
·
-
132 votes
An error occurred while saving the comment Jerry Jackson
commented
This would be a very useful addition.
Related/Duplicated post:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31994488-spoiler-fontJerry Jackson
supported this idea
·
-
1,272 votes
The team is working on changes to the desktop client so recently opened tabs are kept in memory, as long as it doesn’t use too much memory.
I will keep you posted as we make further progress.
Jerry Jackson
supported this idea
·
An error occurred while saving the comment Jerry Jackson
commented
Teams effectively has no caching ANYWHERE. Even chat history is painfully slow to try and browse through (up OR down!) :@
-
66 votesJerry Jackson
supported this idea
·
-
30,579 votes
This continues to be on our backlog due to prioritization of other work items. We will update when there is more to share.
Jerry Jackson
supported this idea
·
An error occurred while saving the comment Jerry Jackson
commented
I don't understand how this is a difficult task which is unclear.
How I would implement this:
- (always) Save the channels chat history database file in the SharePoint.
- On move, shift the sharepoint folder associated with the channel to the new teams sharepoint.
- Teams will see a new channels folder associated with the target team, all the files will be associated with it along with the chat history.
- ???
- Profit -
34,827 votes
The engineering team is continuing to work on adding support for multiple accounts on desktop clients. We will first launch support for 1 work/school account and 1 personal account so users can enjoy Teams for work and personal side-by-side. Windows and MacOS. Support for multiple work accounts is still being worked on and will come at a later date.
You can track status via the roadmap here: https://www.microsoft.com/microsoft-365/roadmap?searchterms=68845.
Thanks!
Jerry Jackson
supported this idea
·
An error occurred while saving the comment Jerry Jackson
commented
The only work around for this I have found for this it to use the web client version of the application, and login to the site in different private browser windows (or different web browsers).
I have struggled with this for a long time before Teams, where you couldn't easily switch between microsoft accounts (like you can with google accounts). Even my primary company email address has different microsoft accounts associated to it which is painful. My solution is to be signed into different accounts on different web browsers, I have IE, Firefox and Chrome all running with different accounts, this way I can also access different Teams accounts via webclient (plus the desktop client). Thankfully on my mobile device Samsung has a feature on the Note8 which allows you to have multiple accounts tied to each app (and even have multiple instances running at once) - so effectively Samsung has solved the problem Microsoft can't.
Final note, Microsoft seem to be making this sort of feature harder and harder to achieve recently, at work I have many instances of skype running using the "skype.exe /secondary" command, however this doesn't work on their latest version of Skype, nore are they adding it in any of there other apps (i.e. Teams) :(
-
472 votes
Application load time is something we are continuously working to improve, and the team is hard at work on fixes. We have validated a recent regression in application launch time that will be fixed in the coming weeks.
An error occurred while saving the comment Jerry Jackson
commented
This really is the absolute worse thing about teams. I HATE THIS. I have contemplated making a screen scraper to make the threads and chats not so painful to browse through. Teams is the only program with chat capability I have ever had this issue with. Even msn messenger in the late 90s didn't have this problem. Mother of god please utilise cache, we don't all have gigabit internet connections like Microsoft seems to assume we do.
Related to this thread:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32129674-scrolling-back-in-time-is-painfully-slowJerry Jackson
supported this idea
·
-
1,375 votes
Thank you for your feedback. Our performance team is working on improving the overall performance of the Windows client. We expect to see performance jumps in the latest version of Electron rolling out (Electron 10).
An error occurred while saving the comment Jerry Jackson
commented
This really is the absolute worse thing about teams. I HATE THIS. I have contemplated making a screen scraper to make the threads and chats not so painful to browse through. Teams is the only program with chat capability I have ever had this issue with. Even msn messenger in the late 90s didn't have this problem. Mother of god please utilise cache, we don't all have gigabit internet connections like Microsofts seems to assume we do.
Related to this thread:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31019839-cache-something-anythingJerry Jackson
supported this idea
·
-
202 votes
Currently we have Teams defaulted to show you the first (up to five) channels ever created. If you want to add more channels to your left rail view, just click the ellipses next to the channel name and select “Favorite”. When you favorite the channel, it will then be “pinned” to your left rail under that team name.
Try that and let me know if that meets your needs!
Suphatra
An error occurred while saving the comment Jerry Jackson
commented
Suphatra's work around is just that.. a work around, it wastes so much time. Some of our teams have MANY channels, requiring every user that joins the team to have to manually go through and favourite them all is stupidly inefficient. I don't understand a scenario where you would ever want users not to see the channel by default.. Maybe if there were heaps of channels which don't get any activity.. but surely unpinning would be better than having to pin everything.
Jerry Jackson
supported this idea
·
-
2,964 votes
Thank you for the feedback. Changing the default setting is under review by the feature team, and your feedback is very useful as they are evaluating.
Jerry Jackson
supported this idea
·
-
491 votes
This request is still working its way through the backlog. Nothing additional to report yet.
-WarrenJerry Jackson
supported this idea
·
-
14,912 votes
We have raised the priority of this work item, and it is currently being worked on. We don’t have any dates to share at this point, but will update when we have new status. Thank you!
Jerry Jackson
supported this idea
·
-
1,563 votes
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
-WarrenJerry Jackson
supported this idea
·
This exists now. But the way it's implemented is really annoying. I would like the setting to be optionally as "default only", as in, teams/channels can choose to whitelist additional domains, but by default they would be restricted to the organisation whitelist. Our organisation has implemented the whitelist, however to allow specific emails to a single channel now, the entire organization needs to have that incoming domain whitelisted.. dumb.