-
Notifications
You must be signed in to change notification settings - Fork 358
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
Missing Search/Advanced Search in Ansible Playbooks/Repositories/Credentials page #6765
Comments
@miq-bot add_label bug |
I'm not sure there was ever supposed to be any search or advanced search there. I think what you're seeing is a screen with no search, and a default listnav which just says no filters. (IMO it doesn't sound like a bug, but once we have support for listnav-less layouts, we may want to use them here.) |
@himdel So from what I understand, the bug here for now is the misleading text in accordion. |
@hstastna it looks like we should not render listnav partial for these screens. |
@hstastna having nameonly search makes sense on all list views, but listnav should only be visible if we list can have advanced search, without advanced search there is no way a user can add filters to the screen. So, we should make changes to code to display nameonly search on the screen and hide the listnav when advanced search is not allowed. |
Linking with #6356 Maybe instead of adding search to the no-listnav layout, we can move simple search to toolbars. |
I like the idea about moving Search to toolbar but according to the comment it's faster and easily doable to just add the existing Search to the layout, at least for now. |
Fixed in #6810 |
Go to Automation > Ansible > Playbooks/Repositories/Credentials page and you can see that in accordion, there's No filters defined. (or maybe some filters already?) but you cannot define any filter because of missing Advanced Search button on the right of the page.
Also it is not possible to search through items in the list. Search not present, too:
The text was updated successfully, but these errors were encountered: