-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes stage filter not working in Kanban View ( #5496 ) #6896
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This pull request addresses the issue of cards disappearing when moved to filtered stages in the Kanban view.
- Modified filter logic in
useLoadRecordIndexBoardColumn
hook to prioritizerequestFilters
over column-specific filters - Ensures cards remain visible when moved to filtered stages in Kanban view
- Improves consistency of card visibility across different board columns
- Addresses core functionality issue in the Kanban board drag-and-drop feature
1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings
const filter = requestFilters | ||
? requestFilters | ||
: { | ||
[recordIndexKanbanFieldMetadataItem?.name ?? '']: isDefined( | ||
columnFieldSelectValue, | ||
) | ||
? { in: [columnFieldSelectValue] } | ||
: { is: 'NULL' }, | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: This change allows for more flexible filtering, but ensure it doesn't break existing functionality in other parts of the application that rely on the previous filter behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I'm surprised, it seems requestFilters already contains everything and we can actually use it directly.
Maybe @lucasbordeau you have more knowledge about this part?
Otherwise it seems to work
@Weiko I checked the gitblame and the context is this: 2cd624a So the above fix seems incorrect because it'd probably break the "No value" column results when we apply filter. I'm open to just hiding the kanban field from filters if it's easier and clean in the code. Both options are okay. |
Hey @Faisal-imtiyaz123 closing since it wasn't addressed after my previous comment. Thanks for the attempt! cc @magrinj I think when you refactor viewGroups/Kanban this might solve the above issue |
fixes #5496