Make rename in Teams reflect name changes in Sharepoint?
When I rename a folder in the Teams app, the underlying folder is not renamed in sharepoint. This is most confusing.
Quick update on this suggestion. We are still working on this with MS Teams. We don’t have an ETA to share still.
Mark R commented
Any update on an ETA?
Please give us an updated ETA on this critical bug fix. I agree with everyone's comments, this should be pushed up in priority at MS since it's is starting to be a real issue in our large OEM who adopted Office 365 with the promise that it'll get continuous improvements and updates to fix these kinds of things. We create a Teams channels for each new projects/products that we want to potentially launch to our customers, and we use default prod dev sequential codes for each potential project/product name (and Team channel name, at least initially). We only give proper names for those projects/products that get past a certain phase and will actually end up being provided to our customers, so we need to be able to rename the Teams channels and get the SharePoint folders to be automatically renamed as well, else things break down and become hard to find...
Growing more impatient every day this persists... C'mon y'all, this is a huge priority for all your users!
New Year same BUG. Teams Uservoice was last updated in Dec 2018 with...
"Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra"
Now here the last update is from May 2019 saying we have no ETA.
What's up? This is a major problem that has caused many headaches for us using Teams as our primary collaboration tool. Especially when we have the corresponding Sharepoint folders synced through OneDrive.
This is not a feature but a BUG! Please either fix this or *disable* the channel renaming option for good. It only creates hug messes and make user stay away from Teams. And we are all amazed by how MS responses to such a fundamental and critical issue impacting so many users - especially considering those are mostly IT Admins who are trying hard to introduce a new MS product to their companies.
Teams developer: "We stand on shoulders of every MS applications!"
SharePoint developer: "Hmm this is not our problem but a Teams issue."
User: "Let's uninstall everything and get back to Slack."
Chris Conley commented
The Teams UserVoice channel confirmed that the SharePoint team is working on this. (My guess is that the Teams development team reads UserVoice more than the SharePoint development team does.)
Even though MS says they're working on this, maybe they are not since this is really an issue with Teams even though it uses a SharePoint document library. Everyone who has voted for this here should also vote for this on the Teams UserVoice at https://microsoftteams.uservoice.com/forums/555103-public/suggestions/38916427-rename-of-team-channel-doesn-t-rename-associated-s which only has two (2) votes.
Today is the first anniversary of MS working on this problem. It seems to be that there are quite many users experiencing some issues here, so perhaps it's a good idea that Microsoft gives it a bump and some developers ...
any updates - already struggling to get users to adopt teams - this just makes it harder
Scott Péron commented
Any news, updates on this? We're encountering this too.
Esko Bar commented
This thing is a disaster. Teams must know it and Sharepoint must know it. Makes me reconsider switching to Teams.
Not fixing the bug is one thing, but not responding to users is exponentially worse. This is a slap in the face to customers.
I'm not sure how items like this actually get past QA.
6 months later, any updates on this?
Or are you playing ping-pong with the Teams developers?
Incroyable de maintenir un tel niveau de confusion.
Fixez une bonne fois pour toute qui est maître.
#spoil : la bonne réponse est Teams !
I cannot for the life of me believe this is considered a Feature Request. This is a bug, 1000 times over. This is currently and will continue to cause mass amounts of confusion. Worse yet, there is no way for IT to help employees once it happens.
Get it fixed, Microsoft.
Any news on this?
Deb W commented
This is sooo frustrating.
What is the status about this rename issue
Ingvill Greve commented
Can you please share a status on this issue, this is affecting a lot of users.