A channel with that name already exists about mattermost HOT 33 CLOSED

The issue still exists!

from mattermost.

The issue is closed 3 years ago, but the problem is still there :(

from mattermost.

Still no fix four years later?

from mattermost.

Issue still exists omegalul

from mattermost.

I'm still seeing this issue today (Oct 2018)... I was asked to create a channel. Slack says that the name is taken but there is no channel (not even archived) group or username with that name. I'm also a Workspace Owner.

from mattermost.

Still the same issue 5 years later

from mattermost.

2021. The issue still exists.

from mattermost.

@thearabbit it's not related to this repo (but is's the first Google result for that Slack error), so if you never got an answer, you need to change the filter to "Archived Channels" to see Archived channels in search:

Sorry for the noise!

from mattermost.

Also ran into this today

from mattermost.

Thanks @Usernot,

A fix is queued for this by changing the error message to "A channel with that name was previously created". There's a new set of functionality coming up that will not delete channels, but instead archive them, allowing histories to be restored. As part of this, once the name for a channel is taken, a new one cannot be created.

The workaround is to rename the original channel.

@rgarmsen2295 this is ticket MM-1416 internally,

from mattermost.

Thanks @santiagomoneta - this particular project is for Mattermost, an open-source messaging and collaboration platform (https://mattermost.com).

For Slack questions, would you be open to visiting their help forums?

from mattermost.

The issue still exists :(

from mattermost.

fixed with #143

from mattermost.

"There's a new set of functionality coming up that will not delete channels, but instead archive them, allowing histories to be restored."

@it33 is this still being planned? channel deletion is a hot issue in the feature request forum

from mattermost.

Thanks @tomtruitt for the feedback, we have a Jira ticket where you can track progress of this feature.

from mattermost.

@jasonblais I've upvoted that Jira ticket and am watching it. Definitely hoping for this to be included in the next release. :) Here's my story if it helps.

Tried importing data from Slack into a fairly fresh instance of Mattermost. If a channel already existed with the same name in Mattermost, the Slack data was not imported into that channel. Sort of makes sense; importer's in beta, I'm sure there are lots of kinks to work out.

To rectify my issue, tried deleting all channels in Mattermost and tried importing same Slack data again. This time, all imports failed. Again, figured this was just an importer-in-beta bug.

That's when I decided just start using Mattermost by recreating the channels and using them with a blank slate. But couldn't recreate the channels because the names were already taken. That's when I realized that's why the data import failed for channels that already existed too.

Properly labeling the menu option as "Archive" instead of "Delete" would be a first step. Are there other issues/tickets already logged for unarchiving channels, as well as more gracefully dealing with channel imports when pre-existing channels have the same name as channels to be imported? I'll totally upvote those too. :)

from mattermost.

I have the same problem

But when I tried to search channel name, it don't have

from mattermost.

Haha

from mattermost.

Thanks for the feedback all!

@xaionaro We're tracking the feature with this epic, which adds channel archives https://mattermost.atlassian.net/browse/MM-354

@thearabbit The UI screen you shared seem different from Mattermost. Is that from Slack by any chance?

from mattermost.

Sorry, This is on Slack

from mattermost.

Sorry

from mattermost.

Any further updates on this? Is there a script which can be used as a workaround to delete the channels from DB?

from mattermost.

Thanks @niks3089 for the follow-up!

Our command line tool supports the following two use cases:

1. deleting a channel -- note that this would also delete all messages within that channel
2. restore the channel, then rename the channel and archive it.

Some of these, if not all, are also be available through the API.

For this particular feature proposal, would everyone be open to contribute this in the feature idea forum so it can be discussed, upvoted and considered for a help wanted?

Please include a link back to this GitHub Issue. If you're interested in implementing, please say so and we'll prioritize the review.

You get 10 votes in the feature idea forum, and each one influences the future of the project.

from mattermost.

The issue still exists

from mattermost.

Yeah, many years later, pretty frustrating. Doesn't look like there is a solution either. Time to find another communication app for small dev groups.

from mattermost.

Wow, this still exists. Just ran into this problem

from mattermost.

fixed with #143

@coreyhulen : May be worth re-opening the issue? :)

from mattermost.

please reopen this issue and fix it as it's still around :(

from mattermost.

Guys I found the issue.

So basically the channel still exists, try to use the search bar to search that channel. Once you find the channel, join it and then delete it manually from settings. This is not an issue, but just an unfriendly behavior. Hope this helps

from mattermost.

No, this issue still exists, because the offending channel could be private with nobody in it, and there is no way even for workspace admins to fix the issue. It isn't possible to even find the channel in the list.

from mattermost.

I still see this issue...

from mattermost.

cc @amyblais

from mattermost.

As the thread here is long and I'm seeing this report for the first time, would someone be open to creating a new Issue via https://github.com/mattermost/mattermost-server/issues/new with the below details?

1. Your Mattermost server version
2. Detailed reproduction steps
3. Observed behaviour
4. Expected behaviour

from mattermost.