@adam deltinger So lets say I have had aconversation with a colleague running for a year now.
Ctrl + F ... search for a part of a document name and I get a list of results (eventually after a long delay).
that's where the "good" ends.
I click on a result item ... and teams either freezes, crashes, or seems to be thinking about what to do for seemingly forever.
If the colleague in question then says somethign in the conversation whilst this is taking place when it finally decides what it wants to do it results in just taking me to the new message.
If the colleague doesn't say or do anything the search still doesn't seem to take me to what it found.
It's like it's working on a fragmented index or something and taking me to the wrong part of it.
Classic example just today was looking for a document we wrote about 6 months ago.
It fairly quickly found references to the document in our chat history but out right refused to take me to the results of the search when clicked on.
I've had this experience from teams since day 1 of using it ... it's never changed I assumed it was because teams was new when I first discovered it and over time just learned to work without it.
But given how I use the same feature in discord ... I'm starting to realise it's a MUST have feature the more history you have in the system.
It's also worse, the more history you have in the system.
