We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
A survey was issued, and I answered it. But I am very concerned that there is a misunderstanding. The survey only mentions a compact mode for teams / channels list. That is not the biggest issue.
-> We need a compact mode for the messages.
This request is still on the backlog.
Waiting for this. One use case:
- Working on user story #US123, which has been reported through #BUG789
- Oh, I remember we saw this problem in #BUG789
Click #BUG789, get all conversations which ever mentioned #BUG789. Including integrations (eg GitHub).
The feature team is still investigating this item and a decision has not been made yet.
@Warren, having team chat and other Microsoft Teams capabilities without this is totally missing the ChatOps train. Should we look at hosting a mattermost or something equivalent in parallel for ChatOps use cases because MS Teams does not support websockets to allow on-premise bots?
There has been some discussions and even an Hubot adapter: https://github.com/Microsoft/BotFramework-Hubot
But this only support bots on the public cloud.
We are looking for guidance.
Bot can be Hubot, Lita, Cog, ...
Without this, actual "ChatOps" kind of capabilities are not available.Olivier Jacques shared this idea ·
This item is still on the backlog. I’ve received no further updates yet about this topic. I will continue to bring your feedback to the feature team.
Indeed. Multiple use cases to allow bots to listen to activity in a room:
- Augmented conversations - add details when a bug or user story is mentioned
- Conversational User Experience: with the current implementation, I am not sure that conversational user experience (https://docs.botframework.com/en-us/, https://www.luis.ai/home/index) can actually be implemented. I have not tried though.
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.
Agreed. Desktop client on windows is almost always top CPU usage on my i7 laptop. Clicking around, and memory consumption goes up very fast (~450Mb), yet seems to go back to 230Mb after. There is a lag when changing channel as well.
We know so many of our customers use Linux and we want Teams to be available for everyone. Stay tuned for more information soon.