Describe the Bug
When filtering a collection table on a relationship field using "is in" it behaves just like the "equals" option.
Link to the code that reproduces this issue
https://github.com/stofolus/payload-filter-in
Reproduction Steps
Use the base template. Add the following fields to the media collection
{
name: 'user',
type: 'relationship',
relationTo: 'users',
},
{
name: 'language',
type: 'select',
options: ['en', 'fr', 'es', 'de', 'it', 'pt', 'ru', 'zh', 'ja', 'ko'],
},
Try to filter using "is in" on both fields. My expectation is that it should work in the same way
Which area(s) are affected? (Select all that apply)
area: ui
Environment Info
Binaries:
Node: 22.13.0
npm: 11.0.0
Yarn: N/A
pnpm: 10.8.0
Relevant Packages:
payload: 3.58.0
next: 15.4.4
@payloadcms/db-mongodb: 3.58.0
@payloadcms/email-nodemailer: 3.58.0
@payloadcms/graphql: 3.58.0
@payloadcms/next/utilities: 3.58.0
@payloadcms/payload-cloud: 3.58.0
@payloadcms/richtext-lexical: 3.58.0
@payloadcms/translations: 3.58.0
@payloadcms/ui/shared: 3.58.0
react: 19.1.0
react-dom: 19.1.0
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP Tue Nov 5 00:21:55 UTC 2024
Available memory (MB): 30891
Available CPU cores: 16
Describe the Bug
When filtering a collection table on a relationship field using "is in" it behaves just like the "equals" option.
Link to the code that reproduces this issue
https://github.com/stofolus/payload-filter-in
Reproduction Steps
Use the base template. Add the following fields to the media collection
Try to filter using "is in" on both fields. My expectation is that it should work in the same way
Which area(s) are affected? (Select all that apply)
area: ui
Environment Info