Repository navigation
Make the Admin Console default page size configurable #50681
Replies: 1 comment 2 replies
|
I prefer solution #1 using local storage. This seems to me like an individual user preference that should not be stored on the server side. It would be a nice little enhancement. I also think the preference should be saved on a per-table basis. It's very likely that the user's preference for one table is different from the preference on another table. Please submit an enhancement request against the admin console. |
|
Thank you for the reply. I opened a Issue #50710. I hope its the correct way of doing it like that in this project. |
@andreas-kolbinger From now on, when you open an issue, use the "New issue" button. Then all the proper labels will get assigned and the issue can go through our workflow. I've set the labels manually, so we should be good now. |
Uh oh!
There was an error while loading. Please reload this page.
Description
In the Admin Console, list views (e.g. Users, but also Clients, Groups, etc.)
default to 10 records per page. A user can change this manually to 20, 50, 100,
but the selection is not remembered, after a reload it falls back to 10.
Motivation
For admins who routinely browse larger realms, 10 rows per page means a lot of
extra paging for every session. Being able to see 20 (or more) by default would
noticeably reduce clicks for day-to-day administration.
Proposed solution
Either of the following would solve it (in order of preference):
(e.g. in localStorage) so it is reused across reloads and across list views.
This is the simplest and most user-friendly option.
an admin-configurable default page size.
Additional context
resets on reload.
js/apps/admin-uilist/pagination componentsAll reactions