Jerry Jackson
My feedback
-
8,198 votes
We acknowledge the demand for this capability and are exploring the best possible solutions to enable this.
~Alex
-
15 votesJerry Jackson
commented
Existing ticket for this already.
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31019839-cache-something-anything -
127 votesJerry Jackson
supported this idea
·
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.
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.
-
6,267 votes
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
~Alex
Jerry Jackson
commented
'Scrolling back in time is painfully slow' has been merged into this idea
Thanks for nothing Microsoft. That issue was very specific, the chat history (or lack thereof) is painful, and completely stupid. This ticket however is relating to the memory/cpu overhead/performance. The lack of chat history caching is the root problem in the ticket you blindly merged here.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
·
-
219 votesJerry Jackson
supported this idea
·
-
1,353 votes
This feature is still on the backlog.
-Warren
Jerry Jackson
commented
24 hour time please.
Why not just follow the system time format?
Jerry Jackson
supported this idea
·
-
58 votesJerry Jackson
supported this idea
·
-
1,174 votes
The feature team is still working away on this feature request. No new updates at this time.
-WarrenJerry Jackson
supported this idea
·
-
35 votesJerry Jackson
shared this idea
·
-
9 votesJerry 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
·
-
12 votesJerry 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
·
-
588 votesJerry Jackson
supported this idea
·
Jerry Jackson
commented
Teams effectively has no caching ANYWHERE. Even chat history is painfully slow to try and browse through (up OR down!) :@
-
34 votesJerry Jackson
supported this idea
·
-
8,638 votes
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.
~Alex
Jerry Jackson
supported this idea
·
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 -
10,429 votes
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.
~Alex
Jerry Jackson
supported this idea
·
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) :(
-
39 votesJerry 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
·
-
152 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
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
·
-
908 votes
This item is still being reviewed and pending a decision. No new details at this time.
-Warren
Jerry Jackson
supported this idea
·
-
371 votes
This request is still working its way through the backlog. Nothing additional to report yet.
-WarrenJerry Jackson
supported this idea
·
-
3,732 votes
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
Jerry Jackson
supported this idea
·
I have started ignoring peoples messages because I am editing a document or wiki and as soon as I go to a chat I lose document context. Who the **** thought only being able to read/edit a document (X)OR chat was a good idea?
>:[