If user A has visibility and edit privileges to hostroup "all/FooBar" but not to the hostgroup "all", then user A edits, for example a parameter override for hostgroup "all/FooBar" and then saves, the hostgroup is removed as a child of "all" and becomes just "FooBar".

Upon futher inspection when first opening up the edit dialog for hostgroup "all/FooBar" the parent hostgroup drop down has been emptied and if selected only lists hostgroups that user A has access too.

The expected functionality would be that if a child hostgroup, such as "all/FooBar" is already a child of another hostgroup, in this case "all", even if user A does not have visibility to all, FooBar should not be removed as a child of "all" when user A saves other changes to "FooBar".