Olivier Jacques
My feedback
-
16,913 votes
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.
An error occurred while saving the comment Olivier Jacques
supported this idea
·
-
5,986 votes
This feature is on the backlog. I will update you when we have more details to share.
An error occurred while saving the comment Olivier Jacques
commented
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 #BUG789Click #BUG789, get all conversations which ever mentioned #BUG789. Including integrations (eg GitHub).
Olivier Jacques
supported this idea
·
-
366 votes
We have a solution for this ask and have moved this on our backlog! Keep watching here for updates as we get closer to completing this work.
An error occurred while saving the comment Olivier Jacques
commented
@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.
An error occurred while saving the comment Olivier Jacques
commented
Bot can be Hubot, Lita, Cog, ...
Without this, actual "ChatOps" kind of capabilities are not available.Olivier Jacques
shared this idea
·
-
229 votes
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.
-Warren
An error occurred while saving the comment Olivier Jacques
commented
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.Olivier Jacques
supported this idea
·
-
35 votesOlivier Jacques
supported this idea
·
An error occurred while saving the comment Olivier Jacques
commented
-
14,001 votes
Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.
An error occurred while saving the comment Olivier Jacques
commented
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.
Olivier Jacques
supported this idea
·
-
323 votes
Hi guys! Thanks for submitting this. I totally hear you and have experienced this as well.
The good news is, we’re actively working on this. We recently pushed an update that improved performance when channel switching and scrolling. So this should be considerably better for you.
We’ll continue to make improvements on performance, so stay tuned for updates.
Keep the suggestions coming and thank you for helping us make Teams awesome!
Sincerely,
SuphatraEmail: sparavi@microsoft.com
Twitter: @skprufoOlivier Jacques
supported this idea
·
-
38 votesOlivier Jacques
supported this idea
·
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.