@dericeira It looks like it hasn't been implemented yet. It should be possible to tie things together using the parent_id for a subgroup to determine it's parent group.
Would you be willing to provide this functionality by creating a Merge Request for the Community Edition project?
@dericeira Each group result will have an id and a parent_id attribute. If this is populated (not null), you know that the group is a subgroup and not a top-level group. You can use this ID to match up it's parent and build up your tree of groups.
@markglenfletcher Got it. This is weird. In my company we have a private repository with about 10 subgroups, totaling more than 250 projects. On this route I can only list the parent repositories. I don't know, but maybe It will only work with public groups.
Not a possible. I have owner status in all groups and subgroups. I am using the correct access key, on /groups route I can only see the 3 main groups of our parent group.
@markglenfletcher, I am experiencing the same issue as @dericeira. From the public API, https://gitlab.com/api/v4/groups, I see the results with subgroups listed. Inside my company we are using the GitLab Enterprise Edition (9.4.4). I do not see any subgroups with a similar request. If I include ?all_available=true, I do get subgroups. However, I will now need to sort through several hundred groups to find the groups and subgroups I am interested in. This is too cumbersome.
@justgrumpy Yes, the example is merely a workaround for the current implementation. The feature proposal here still stands to implement this properly to list subgroups beneath the parent group.