N°903 - Portal : Search / Filter on Browse mode mosaic#861
N°903 - Portal : Search / Filter on Browse mode mosaic#861Sbleut wants to merge 3 commits intoCombodo:developfrom
Conversation
Allow users to filter mosaic items dynamically while typing. Search operates case-insensitively on name, description, and tooltip title. Reset filter automatically when navigating between mosaic levels.
|
Hello @Sbleut thanks for the PR! Could provide screenshots of the UI without and with filtering so we can see how the items are displayed if:
|
|
Thanks for the screenshots @Sbleut , it is just missing the "Items from different levels match" use case. In list and tree mode, you can filter all levels at once. If we add filtering to the mosaic view as well, it must do the same, not a 1-level filtering only. That's why we didn't made it in the first place, as we didn't really now how to display it. So in order to move forward with considering the PR, we need to see an example where you have items matching the filter in the 3 levels "Service Family", "Service" and "Service Subcategory" so we can see how it will display when displaying matches for different levels at the same time. :) Or does the filtering only works for the level currently displayed? |



N°903 - Portal : Search / Filter on Browse mode mosaic
Allow users to filter mosaic items dynamically while typing. Search operates case-insensitively on name, description, and tooltip title. Reset filter automatically when navigating between mosaic levels.
Base information
Objective (enhancement)
In the Browse Brick of the portal (mosaic mode), when many service families or services are displayed, it becomes difficult for end users to quickly find the item they are looking for.
Proposed solution (enhancement)
Add a dynamic client-side search field above the mosaic content.
Filter behavior :
data-original-title)Tests
This change impacts the portal mosaic UI only (Twig + client-side JavaScript).
No PHP unit tests were added because the feature does not introduce
backend logic, API changes, or data model changes.
The behavior was validated manually in the portal by testing:
Checklist before requesting a review
Checklist of things to do before PR is ready to merge
Things that needs to be done in the PR before it can be considered as ready to be merged