fleetdm
Choose number of rows displayed in table views in Fleet UI
Problem
As an IT admin, I want to see many of my hosts, software, vulnerabilities, queries, and policies in one table view without my results being paginated.
Currently, Fleet limits to showing the following before pagination: 50 hosts 22 policies (and possibly queries. I was not able to confirm in Dogfood) 20 software titles 20 vulnerabilities
What have you tried?
I looked for a way to change the number of rows displayed in table views in the Fleet UI, but did to find any options to do so.
Potential solutions
In the Fleet UI, there could be a setting or dropdown to change the number of rows that get displayed in table views. This would allow admins to view more data at once before needing to click to another page.
What is the expected workflow as a result of your proposal?
In general, this is more of a "quality of life" feature request and it does not unlock any workflows that are not in the product today. However, this could help with selecting devices for bulk actions like deleting/moving hosts to a new team or deleting queries. Currently, if I click the checkbox in the header row to select all devices in the table, the max I can select is 50 hosts. So if I have 100 hosts I want to move to a new team, I have to perform the action to select all hosts displayed on the page and move them to the new team twice.
Thanks for tracking this one @ddribeiro!
Currently, if I click the checkbox in the header row to select all devices in the table, the max I can select is 50 hosts.
Heads up that today, you can select hosts across all pages using the "Select all matching hosts" option.
Would this work for the customer's use case?
22 policies (and possibly queries. I was not able to confirm in Dogfood)
I think it's 20 policies before pagination. We should be seeing the total count at the top of all tables. If not, I think that's a bug.
@ddribeiro @pintomi1989 we're removing this issue from the feature fest board as there is no engineering capacity to take it on at this time. have you reviewed noah's suggestion above? please tag me back in if this becomes workflow blocking
