The best way to explain this would be to say that sometimes the IS / IS NOT filter for single/multi select column fails to filter all the relevant values.
However, when anyone tries to click any field in the row, which has not been picked up by the filter, suddenly, the filter starts to work for that row, as shown in the screen recording.
at the moment, it’s hard for me to replicate this issue consistently, it may be related to stacking filters or using multiple filters in many views. Will report if I find sth more - but please let me know if this issue corresponds with any of the known bugs. It was observed in 1.26.1 and prior (self hosted - for both default and custom configs)
both this bug and the other linked one seem to be related to the issue with importing tables from Airtable.
However, I cannot reproduce it locally, making it difficult to pinpoint the cause. Would it be possible for you to share the link to the Airtable base so I can conduct further checks? If there is any sensitive data, please replace it with dummy data and send the link privately to me.
@davide This table has not been imported via Airtable, so seems like a separate issue.
The data in this one has been imported via CSV (originally from Excel)
The issue in the Airtable import is persistent (if it happens, it is repeatable until one changes the value) while the issue in this one seems to disappear after page reload and is not always visible.
According to a few people on my team this happens occasionally after a longer “session” with heavy filter use, but they have not observed any more patterns.
In this case, I have no idea how to replicate it, and AFAIK, we don’t have an issue in our backlog for this bug, but if you have more information, please share it with us so we can promptly fix this issue.
Next time it happens, can you please verify what happens when you refresh the page? Does the view show only the correct data or do you still see the wrong data? Or maybe the filters are not there anymore?
Is this a public or personal view?
it’s hard for me to replicate this issue consistently, it may be related to stacking filters or using multiple filters in many views.
In the video, it appears that there is only one filter being used, so I would say that the issue is not due to stacking filters. Filters in other views cannot affect the results of this view, as they are entirely separate objects, so I don’t think it’s related to other views either.
However, when anyone tries to click any field in the row, which has not been picked up by
the filter, suddenly, the filter starts to work for that row, as shown in the screen recording.
This is because the UI performs some further checks to ensure the data matches filters before sending the updated data to the server, but the main problem is that given that filter, you shouldn’t see rows containing the filtered-out option in the first place.