-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Device Filtering on the Details Page is broken after version 23.7.22 #627
Comments
This should be fixed in the next release. If you can, please have a look at the It would be great if you could test this (backup everything first or use a new container) on your end by switching to the above image and letting me know if the issue was resolved. Thanks in advance, |
HI @jokob-sk , thanks for the prompt update. However the fixes are not working. I also noticed that if i don't do any filters after i enter to any device details the global number of devices only lists 1 |
It seems there is a process in the background that normalizes something that has to do with these filters, after coming back for a walk a tested and now the filters are working as expected. |
Thanks for testing, appreciated! |
released 🚀 -> closing |
Is there an existing issue for this?
Current Behavior
On the Devices section, any type of filter from the dashboard boxes or from the search box works to narrow the list of devices. But if you click on any device from the filtered list, you are no longer on the same list but on the global list.
So your total number of devices will equal to the total number of devices and not the total number of devices from your filter.
Expected Behavior
On this example i will show how the filtering was working on the version: 23.7.22
We have a total of 110 devices
Then if we search for extreme we narrow the list to 8 devices.
If we click on any of the devices from the list.
The filtered items remain and you can move between the filtered items of the list.
Steps To Reproduce
No response
app.conf
No response
docker-compose.yml
No response
What branch are you running?
Production
app.log
No response
Debug enabled
The text was updated successfully, but these errors were encountered: