Template Groups not working as expected

Here we are again with Template Groups. The more we try to use them, the more it seems difficult to understand the way they should work.

Previously, before they were introduced, it was possible to create templates having sub-connections, and those templates could be managed completely, also in terms of appearance. They could also be used with the Edit / Edit (Special Actions) / Convert with Template contextual menu, which was a life saver when a template had to be modified / enhanced, and then re-applied to all the entries which were using the previous version.

All of the above is not available with Template Groups, or at least we don't understand how they should be used. We have already reported that currently there is no way to define the icon the templates have: those that were created during the migration of sub-connections in a previous version of RDM inherited the icon from the ancestor node being converted, but every other one created by the user has no way to modify this feature. Contextual menus on the templates editor are not very intuitive, too.

Then there is the big limitation that the Template Groups DO NOT appear within the selection windows of the Entry Conversion with Template, and this zeroes more than half of value of groups. Unfortunately, it is not anymore possible to create sub entry (as it is now called the previous sub-connection) within a template entry that is not in a template group, hence a functionality that existed before the introduction of the Template Groups has been lost now. I fail to understand why there is such limitation in the templates, and also why it is not possible to move/copy a template entry from a Template Group to another one.

Our take is that even with version 2023.2.22.0, which we are currently using, Template Groups are still an half-implemented concept that has been released in a rush removing, instead of at least equaling, functionalities previously available.

I apologize for the semi-rant. Thanks.