Apr 07 2021 06:31 AM
Apr 07 2021 06:31 AM
The SharePoint Roadmap Pitstop: March 2021 post (posted 3/31) included the following:
I've tested this in two different tenants (one standard, one early release) and the issue has not been resolved. There's no corresponding roadmap item, and no update has been posted to the two UserVoice items here and here.
Has anyone had luck seeing this fix in their tenant, or have any more info on when we can expect this to take effect? This is a huge problem that is causing lots of headaches in many orgs and has been on the backlog for around four years, so I'm excited to finally seeing it possibly getting resolved.
Apr 07 2021 07:51 AM
Apr 14 2021 05:46 AM
Just bumping this, as I was really hoping to hear from the product team on why this long-awaited bug fix was announced as fixed, but seemingly has not been. Thank you!
Apr 14 2021 06:16 AM - edited Apr 14 2021 11:43 AM
Apr 14 2021 09:53 AM
Apr 26 2021 10:55 AM
Apr 27 2021 07:50 AM
Apr 27 2021 10:56 AM
@PhoenixMS - Hard to tell what that roadmap item is going to do since it's incredibly vague.
Apr 29 2021 05:56 AM
There's now a roadmap item for this issue!
Microsoft Teams: Pairing the channel and the corresponding SharePoint folder name.
When renaming a Teams’ channel, the corresponding SharePoint folder will be renamed and reflect the new name. This will help create consistency across Microsoft 365 endpoints, making it easier on users to find their files from anywhere. This new feature will be available for all Standard and Private channels. For Standard channels – The corresponding folder in SharePoint will be renamed. For Private channels – The corresponding site name and the folder in SharePoint will be renamed. For legacy Teams channels that were renamed prior to this rollout, there will be no change in experience. When a legacy channel is renamed after this release, it will simultaneously rename the corresponding SharePoint folder.
Apr 29 2021 06:12 AM
Jan 11 2022 07:45 AM
Feb 28 2022 02:39 PM
Feb 28 2022 05:30 PM
Mar 24 2022 11:19 AM - edited Mar 24 2022 11:23 AM
For this bug correction, there is still a problem to fix. After a change in the Team or channel name, there is a delay on the share point update, but this is not so critical. The main problem is that on the "my Sites" side bar, the old name is still there and don´t get updated at all! @PhoenixMS
Regarding this bug: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=72211
Mar 29 2022 02:29 PM
@PhoenixMS I am trying to resolve a problem similar to what I'm reading here in this message.
A few months back we changed the name of a teams channel from “Youth Groups” to “National Youth Missions”. When we did that it did not change the file folder host name from “Youth Groups” to “National Youth Missions”. One of our teammates was trying to correct that and decided to change the name of the folder manually on his Mac through the Finder synced files. I believe this essentially made the change at the SharePoint location which started a mess. As I'm sure you know, the name change created the new “National Youth Missions” folder and moved all the files but it disassociated the files from “National Youth Missions” teams channel.
Now, our “Youth Groups” folder that is hosted in the “National Youth Missions” Team channel is empty. The original files are still in the new folder that was created called “National Youth Missions” but are not associated with the channel. We'd like to try and keep the teams channel “National Youth Missions” and change the host folder in that channel to the “National Youth Missions” folder that now holds all the files. However, we are not sure that is possible or can be fixed.
According to the Microsoft 365 Roadmap site, "For legacy Teams channels that were renamed prior to this rollout, there will be no change in experience. When a legacy channel is renamed after this release, it will simultaneously rename the corresponding SharePoint folder." I suspect this we are in the no change to experience group since this problem occurred several months ago. I think I understand and have read things through on this topic but I may have missed something or there is an answer out there I have overlooked. What recourse do we have to correct this problem? Thanks!
Mar 31 2022 04:34 AM
Apr 06 2022 09:00 PM
@PhoenixMS do we know if this has been resolved yet?
Apr 26 2022 10:57 PM
@Carey_Tuhaka no, the issue is still there. I just tried it. :(