It is very helpful if you can move the under collections with the “main collection”.
Hey there, are you referring to creating nested collections?
Coming from Keepass to Bitwarden for our company we imported our Keepass database into Bitwarden. This created lots of new collections which i nested under a collection called “Imported” so we have a chance to weed out old passwords that are no longer needed.
We found that when we wanted to change where a collection was located it only moved the parent collection and leaves behind all the nested collections that where under it. This becomes impossible if you have a large collection of nested collections and entries. Rather than a 1 click operation it becomes, 10-15 clicks depending on how many nested collections you have.
1 Like
This seems like a very reasonable request and likely what the user would intend.
The primary reason I can think to support the current design is that moving a collection is a big deal, and you never want to move something by accident. That said, I think a prompt that asks “Move all nested collections with the parent collection?” will resolve that issue while still fixing the issue presented by the OP.
Hi, a useful function could be to move collections with subcollections. I don’t see such a possibility at the moment. When you move a parent collection, subcollections skip over the higher collection - they don’t follow the collection being moved. It would be nice if there was a choice whether you want to move only one collection or with subcollections. I hope I explained it clearly 
@bernhard.gschwandtne @seniu123 I merged your posts with this existing Feature Request to the same topic.
Associated with that, I changed the title to a (hopefully) more clear or “obvious” one (before, it was: “Have nested collections move with their parent”).