Rocket.Chat Version: 0.55.1
Running Instances: 1
DB Replicaset OpLog: Enabled
Node Version: v4.8.0
The default selector for channels seems to be gone. This is a big issue for my team as we have an announcements channel.
This put a spook in my wheel as well since I just archived our primary/default channel and now there is no option of making another (new) channel/group the default.
This was implemented in https://github.com/RocketChat/Rocket.Chat/pull/2290 but now is gone...
Confirmed 0.55.1.
It's missing from both user UI and admin/rooms UI, see screenshots:


So is this going to be fixed or what?
Looking for this feature too. Deleted initial #general channel, so I could recreate a fresh default channel. Maybe not the best way to tackle that idea, but I didn't want to have to delete all the hubot test messages one by one. Anyway, perhaps a way to define the default channel in the docker-compose.yml? Tried to pull 0.55.0 and see if I could spin up, with the feature, but didn't see it. +1 thanks. (Next time will just create a scratch channel, and delete that instead, derp)
In the meantime, if you need to set a room to default while waiting for this to be fixed (I'm running in ubuntu snap):
gschwart@rocketchat:~$ sudo /snap/rocketchat-server/current/bin/mongo
Then in mongo shell:
rs0:PRIMARY> use parties
switched to db parties
rs0:PRIMARY> db.rocketchat_room.update({"name":"test"},{$set: {"default": true}})
WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 })
rs0:PRIMARY>
The name of my room in this case is test
This is fixed in 0.56.0 if you're on snap you should now be on that version and the selector already available to you :+1:
Sorry but I had this issue on 0.56 too, so I updated to 0.57.2 and the issue is still there.
I have no button to edit the default channel, @geekgonecrazy if the commit fixed the issue editing ChannelSettings.js, I haven't any file named like this on my installation, so.... I do not understand!
this is back

This issue is still present. There is no button to make a room default in the current version, why is this closed?
this was fixed and then the bug appeared again
last year it definitly worked fine
i think its somewhere in https://github.com/RocketChat/Rocket.Chat/commit/c2ed1e325af38f6d4b2eb6a8452fafa29d8f71db but couldnt find iot so far
In the meantime, if you need to set a room to default while waiting for this to be fixed (I'm running in ubuntu snap):
gschwart@rocketchat:~$ sudo /snap/rocketchat-server/current/bin/mongoThen in mongo shell:
rs0:PRIMARY> use parties switched to db parties rs0:PRIMARY> db.rocketchat_room.update({"name":"test"},{$set: {"default": true}}) WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 }) rs0:PRIMARY>The name of my room in this case is test
THANK YOU for the guide - I`m on v2.4.2 (Ubuntu Snap) and there is no way to set the default status of a room from the UI, so this worked.
Most helpful comment
this was fixed and then the bug appeared again
last year it definitly worked fine