Each instance of a recurring meeting should have separate conversation history
We have a recurring meeting tied to the team's channel and the conversation history has grown way too long over time. Each reply also notifies the accumulation of all participants even if they're not attending the current instance anymore.
We are getting a similar problem. When one person was not part of the recurring meeting invite but was invited to only one event get to see all the Chat messages in that channel. This is a major security breach. We are trying to promote MS Teams as a secure collaboration tool to use countywide, this needs to be addressed as soon as possible. Thanks!
Patrick Dawson commented
This is a major security and privacy risk if a guest attends one instance of a recurring meeting, they get to see the notes of all subsequent meetings, could could a GDPR breach.
DLO from Microsoft commented
Yes, please! This drives my workgroup BANANAs on two fronts:
1. if you open the conversational thread for a recurring meeting, performance degrades sharply in Teams after a few months of recurring meetings - the Teams interface slows down and struggles to incompletely update the meeting history beyond a few hundred entries in the conversational history. Grouping each meeting into its own conversational history would help keep this thread limited in size and would be a welcome performance improvement.
2. If I attend a single meeting, I'm interested in following the commentary for that meeting, and any other meetings I attended. Today, attending any instance of a recurring meeting subscribes you to every single update for that entire recurring meeting until the sequence ends. This seriously annoys guest speakers and occasional SME participants, who now have to see any comment from that meeting in their feed forever. This is the right default notification strategy for core meeting participants, but it's a serious annoyance for guests and SMEs. Since I want to attract guests and SMEs to my recurring calls, this is an unwelcome "attention tax" I'm cursing them with if I ever ask them back again.
Marcin Zwolski commented
If we cannot have new convo each time recurring meeting is started, let's have at least scroll-to-the-most-recent-messages functionality.
One of my recurring meetings was set in March. Everytime I open a chat window - I start with messages from March and have to wait for other messages to be loaded.
Ioannis Bazianas commented
Yes please, we are getting fast to an unmanageable size in the thread.
Marcin Zwolski commented
+1 for that. I've been running recurring meeting for two weeks now, and the conversation history keeps growing... So I would love to see recurring meetings separated with dates or some other label.
Joel Bennett commented
Because the conversation thread for the meeting is the only one you can easily access while you're in the meeting, it's important that there be a new one for each meeting.
Otherwise, when you join it looks like the meeting has been going on for awhile, and there's nowhere for team members to put questions/topics ahead of time for the meeting, much less find a review of the one meeting they missed.
We tried creating a new thread ourselves, but it's a pain to access when you're actually in the meeting, because they're in the same window, and you can't just pop out the meeting and have the channel in a separate window.