The origin of this issue seems : current user was not set in Created group. In 3.X : if an user create a group : he was included in it.

Now : it was not in group, and can add it himself in group …

Confirm the origin of the issue.

In 3.X : current user added (and can not delete himself via GUI)

But we can easily fix to include owner_id for group + for user

But we can easily fix to include owner_id for group + for user

Work for getUserGroupList() function : https://github.com/LimeSurvey/LimeSurvey/blob/3682d8cdc75173957d1e2688c5f86fb3535cae34/application/helpers/common_helper.php#L4146
Not for getUserList function ( https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/common_helper.php#L680 complex to update this one)

@gabrieljenik : you can not add owner_id to user list else you can give access to a group where user was removed from group in 3.X

In 3.X

1. User 1 create UserGroupA (user can see this group) and UserGroupB
2. Superadmin remove user 1 from UserGroupA
3. User 1 can NOT see UserGroupA but still see UserGroupB

Update to 5.X now : no issue User 1 can NOT see UserGroupA but still see UserGroupB

If you fix the owner_id system User 1 can see UserGroupA .

Maybe reset the owner_id when update ? Since it's not used ?

From what I read here, there 2 problems:

Problem 1)
View si retrieveing groups with the wrong query/logic criteria.
New LS5 schema by owner is not used.

Problem 2)
Some old groups created in LS3 could present permission issues with this LS5 logic
Very hard to sharply identify these groups.

I would work on #1 and then somehow show an alert ro superadmins on grups that are candidates #2.

Thoughts?

Problem : User with group creation allowed can not see is own group

Reason :
in 3.X (2.05 until 5.3.28).: we don't use owner_id
In 3.X : when user create group : it was added to group.
In 5.0.0 : we don't use owner_id (OK why not)
In 5.0.0 : when user create group : it was NOT added to group.

Problem 1)
View si retrieveing groups with the wrong query/logic criteria.
New LS5 schema by owner is not used.

It's NOT the problem …
The problem is : We don't add current user when he create a group.

If you add owner_id to permission : this potentially BROKE current permission system. Potentially : some user can see forbidden user name …

Then you need to update API version (5.5.0 to 6.0.0) if you add owner_id to manager UserGroup
My opinion : it can be done only in DEV
And you need to be allowed to update owner via GUI
You can add a complete Permission system (GUI and lot of part of SurveyGroup can be reused)

Like user : my opinion : remove the not really used Update and Delete permission

1. Remove it from definition
2. Remove it i a DB update (set whole to 0)
3. owner can do whole on UserGroup
4. After : manage ALL user group (update / delete) are a new feature.