I’m excited to share that I got to use this in our experimental settings the other day. We’ve built it and are testing it internally. I’ll let you know once it moves up in the validation rings!
We are working on a design with more density in mind. Until this design is solidified we are putting this item back to Under Review.Craig Whelan commented
We've just starting moving our team over to Teams and one of the first remarks of feedback was the screen real estate takes up, it's just not efficient/flexible enough.
We’re updating our command library all the time, so keep checking the menu in the command box to see what’s new by typing / or @.
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.
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
The feature team is still considering this item. No confirmation yet.
-WarrenCraig Whelan commented
Entirely agree with you David
Slack history retention is definitely high on the agenda here when evaluating Teams; not to mention third party application integration (salesforce.com, Twitter and GitHub to name just three...all exist but in very limited form currently it would appear)
Thanks for flagging for the Microsoft team to consider