You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When filtering for more than one attribute filter, it should display the intersection of it. Currently this is not the case (see screenshot). My suspicion is that this has something to do with the "any attribute" filter setting. If condition it on actual attributes I cannot create such an inconsistent state, but am not 100% sure.
Also, if I search for a text in the "any attribute" then this bug does not happen, only if I search for a number (see GIF). There might be other combinations with different operators where this fails, though. But that might be valuable information for bug identification.
To Reproduce
Steps to reproduce the behavior:
Go to data browser in AG News project
Create attribute filter with "running_id" EQUAL 501
Create another attribute filter with "any attribute" CONTAINS 7
See error
Expected behavior
There should be no record displayed as both conditions at the same time are not true on any record
Screenshots
Desktop (please complete the following information):
OS: Win11
Browser edge
Version 1.7.1
Additional context
The text was updated successfully, but these errors were encountered:
Debugging where the error occurs if it is on the FE or BE side and where exactly it happens (1h)
Finding solution why the intersection does not happen (1h)
What problems could be expected? --> I would assume there will be some additional time for debugging/fixing especially if it is on the BE side - less known code (30min - 1h)
UI changes and notifications? --> no additional min/hours
OPTIMISTIC: 2h - 2h 30min
PESSIMISTIC: 3h
SUM: 2h-3h
Steps for testing:
Testing if single filter and filters with intersection work as expected (15 minutes)
Describe the bug
When filtering for more than one attribute filter, it should display the intersection of it. Currently this is not the case (see screenshot). My suspicion is that this has something to do with the "any attribute" filter setting. If condition it on actual attributes I cannot create such an inconsistent state, but am not 100% sure.
Also, if I search for a text in the "any attribute" then this bug does not happen, only if I search for a number (see GIF). There might be other combinations with different operators where this fails, though. But that might be valuable information for bug identification.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should be no record displayed as both conditions at the same time are not true on any record
Screenshots
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: