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

Remember user's pagination preference #3603

New Issue
Closed
opened 2025-12-29 18:30:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:30:05 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Apr 24, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.1

Proposed Functionality

Remember the user's previous selection for "per page" when viewing a paginated set of objects. For example, if the default page size is 50 (as defined by PAGINATE_COUNT in configuration.py) but a user selects a length of 100, NetBox should remember that user's preference and apply it for all objects.

(This feature is actually being implemented as a POC under #3294. I've opened this issue merely to document the feature.)

Use Case

Allows for a slightly more convenient UX.

Database Changes

None

External Dependencies

None

Originally created by @jeremystretch on GitHub (Apr 24, 2020). ### Environment * Python version: 3.6.9 * NetBox version: 2.8.1 ### Proposed Functionality Remember the user's previous selection for "per page" when viewing a paginated set of objects. For example, if the default page size is 50 (as defined by `PAGINATE_COUNT` in `configuration.py`) but a user selects a length of 100, NetBox should remember that user's preference and apply it for all objects. (This feature is actually being implemented as a POC under #3294. I've opened this issue merely to document the feature.) ### Use Case Allows for a slightly more convenient UX. ### Database Changes None ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:30:05 +01:00
adam closed this issue 2025-12-29 18:30:06 +01:00
adam commented 2025-12-29 18:30:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 24, 2020):

Implemented in #4532

@jeremystretch commented on GitHub (Apr 24, 2020): Implemented in #4532
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#3603
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?