starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Don't persist page size preference across views #7670

New Issue
Closed
opened 2025-12-29 20:26:44 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:26:44 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Feb 22, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.4.5

Feature type

Change to existing functionality

Proposed functionality

When viewing a list of objects in the NetBox UI, the user can select a page size to determine how many objects to render in one view. (Default options range between 25 and 1000 objects.) Once a page size has been selected, it will persist as the user navigates to other areas of the application. This FR proposes removing the persistence, so that navigating to a different object view returns the default page size.

Use case

We've found that users will often increase the page size while viewing one type of object for a specific purpose, without realizing as they navigate elsewhere in NetBox that the page size has remained in effect. This can lead to frustration stemming from unnecessarily long load times as many more objects than required are being fetched.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Feb 22, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.4.5 ### Feature type Change to existing functionality ### Proposed functionality When viewing a list of objects in the NetBox UI, the user can select a page size to determine how many objects to render in one view. (Default options range between 25 and 1000 objects.) Once a page size has been selected, it will persist as the user navigates to other areas of the application. This FR proposes removing the persistence, so that navigating to a different object view returns the default page size. ### Use case We've found that users will often increase the page size while viewing one type of object for a specific purpose, without realizing as they navigate elsewhere in NetBox that the page size has remained in effect. This can lead to frustration stemming from unnecessarily long load times as many more objects than required are being fetched. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:26:44 +01:00
adam closed this issue 2025-12-29 20:26:44 +01:00
adam commented 2025-12-29 20:26:45 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Feb 23, 2023):

Would persistence follow the page size preference of the individual user ?

@jsenecal commented on GitHub (Feb 23, 2023): Would persistence follow the page size preference of the individual user ?
adam commented 2025-12-29 20:26:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 23, 2023):

@jsenecal are you referring to the "page length" user preference?

Screenshot 2023-02-23 at 16-13-36 User Preferences NetBox

I think we'd still allow a user to set their global preference this way; we just wouldn't update it automatically when specifying a page size under a specific table.

@jeremystretch commented on GitHub (Feb 23, 2023): @jsenecal are you referring to the "page length" user preference? ![Screenshot 2023-02-23 at 16-13-36 User Preferences NetBox](https://user-images.githubusercontent.com/13487278/221031597-abeb4452-eb7f-4ae9-9afa-dd9a08fd8413.png) I think we'd still allow a user to set their global preference this way; we just wouldn't update it automatically when specifying a page size under a specific table.
adam commented 2025-12-29 20:26:45 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Feb 23, 2023):

Yes, this is what I had in mind. The behavior you described works for me. I would change the description to The default number of objects to display per page however.

@jsenecal commented on GitHub (Feb 23, 2023): Yes, this is what I had in mind. The behavior you described works for me. I would change the description to `The default number of objects to display per page` however.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7670
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?