nextcloud
Can't select "Me (user ID)" in a filter on a "Users and groups" column
Steps to reproduce
- Create a table with a "Users and groups" column that doesn't allow multiple values
- Create a view and add "New filter group"
- Add the "Users and groups" column from step 1
- Add Operator "is equal"
- Select the drop down for "Search Value". It's empty.
If you select a Text column and "is equal" the "Search Value" contains "Me (user ID)" and "Me (name)".
Nextcloud Hub 9 (30.0.5) and all apps updated
Expected behavior
My expectation is that I can filter a list on the rows that are mine or assigned to me since my user ID has been selected in the "Users and groups" column when the row was created or edited.
The "Search Value" should contain "Me (user ID)" for a "Users and groups" column.
Actual behavior
The drop down for "Search Value" is empty for a "Users and groups" column.
Tables app version
0.8.3
Browser
Multiple
Client operating system
MacOS 15.2
Operating system
Rocky 9
Web server
Nginx
PHP engine version
PHP 8.2
Database
MariaDB
Additional info
No response
I confirm the bug report on all of our instances.
Workaround: You can construct the filter in the database manually. Setting tables_views.filter of the matching view to
[[{"columnId":42,"operator":"is-equal","value":"@me"}]]
That is of course no solution for the general user. But we can restrict the problem, that it is an issue of the web frontend.
@MaykGyver is there a way to do that without modifying the database manually ?
That's the issue.
From: Aveyron-RetD @.> Sent: Wednesday, March 19, 2025 9:53:10 AM To: nextcloud/tables @.> Cc: MaykGyver @.>; Mention @.> Subject: Re: [nextcloud/tables] Can't select "Me (user ID)" in a filter on a "Users and groups" column (Issue #1547)
@MaykGyverhttps://github.com/MaykGyver is there a way to do that without modifying the database manually ?
— Reply to this email directly, view it on GitHubhttps://github.com/nextcloud/tables/issues/1547#issuecomment-2735778173, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZJL76JX24AN737FBJKESWD2VEV7NAVCNFSM6AAAAABVNLBXIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZVG43TQMJXGM. You are receiving this because you were mentioned.Message ID: @.***>
[Aveyron-RetD]Aveyron-RetD left a comment (nextcloud/tables#1547)https://github.com/nextcloud/tables/issues/1547#issuecomment-2735778173
@MaykGyverhttps://github.com/MaykGyver is there a way to do that without modifying the database manually ?
— Reply to this email directly, view it on GitHubhttps://github.com/nextcloud/tables/issues/1547#issuecomment-2735778173, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZJL76JX24AN737FBJKESWD2VEV7NAVCNFSM6AAAAABVNLBXIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZVG43TQMJXGM. You are receiving this because you were mentioned.Message ID: @.***>
Same problem here. I cannot even search for my user in the Search field when assigning a user. I think it's the same frontend bug: The search does not show my own account/user.
It's problematic because i cannot assign columns to myself. A workaround would be to create a second account and select my account from this account.
As a workaround, I use another (admin) account to do so. But this is fairly annoying.
This issue might be happening on any "user search input" in the whole Frontend, so a nextcloud bug and no tables big it seems like?
Careful the bug for the self is different and is tracked here, see below. In here in the bug is about that there is no way to filter by a user like in the creator filter. I believe this would be the most useful filter in the tables app.
[+]it's a known bug #1355 [/+] [+]it's followed here https://github.com/nextcloud/server/issues/48180
Careful the bug for the self is different and is tracked here, see below. In here in the bug is about that there is no way to filter by a user like in the creator filter. I believe this would be the most useful filter in the tables app.
[+]it's a known bug #1355 [/+] [+]it's followed here https://github.com/nextcloud/server/issues/48180
You're right, I mixed things up because they are a bit similar.
Not a bug, but a feature request. I intentionally did not add this during the initial User/Group column implementation.
