In a very complex desktop application (such as ours), there are numerous UI elements, some of which even appear multiple times in different locations. The structure of the assigned elements does not always reflect the context in which they are displayed. When working in a specific context segment and searching for a control that has been assigned an alias, it is quite difficult to find it if it was assigned in a different context.
It would be extremely helpful to set up a completely flexible organizational structure for aliases, allowing for duplicate entries in different locations. In my opinion, an alias is merely a placeholder for the associated UI element, so this should be easily possible.
In the current situation, an alias can only be moved up within its own hierarchy path, which is good, but by no means sufficient.