The method of deleting, copying, or highlighting in collection.

The method of deleting, copying, or highlighting in layers.

I began to realize that there is one problem that slows down the process of working in a Blender.

For example :

• You need to make two objects, with a complex hierarchy (Parents)
• First I make one object with a complete hierarchy, when everything is completed, I need to make a copy of everything.

At the same time, in order to do this, I have some suitable options:

• Drop-down menu/highlight hierarchy

-The first and the last (By highlighting with a shift) - Which implies a preliminary disclosure of the entire hierarchy of the object manually.

I think that this is unnecessary manipulation, besides, it is confusing in the workflow, when you get used to intuitiveness (working with keyboard shortcuts), you have to switch to such unimportant little things, it is very annoying.

Therefore, I propose to replace the priority of allocation, between the parent object and the entire hierarchy.

• So that in case of deletion, for example, the "Collection", all its contents are deleted, and not unpacked from it.
• So that when copying, the full collection is copied, and not just the selected parent object (if the hierarchy is disclosed)
• So that any parent object\collection is copied\deleted along with the contents of its hierarchy according to the standard!

(More detailed options, not standard manipulation, can be left for these complex operations)

An additional option: It is quite enough and flexible, it would be to change the selection method in layers.

• There is a method to reveal the entire hierarchy (with the "Shift" click on the arrow), but there is no method to highlight the entire hierarchy of the object \ collection (a combination is needed) - For example, a double click on the object with the "shift".
• Also, in the layer editor it would not be bad to have a standard copy combination (Shift+d)
• Option with hierarchy removal (Shift+x)

There are many variations of execution, but the implementation approach is better visible to developers, it's just an idea to simplify the work and logic of the process.

If such a feature is already being developed or introduced in the latest versions, I apologize!