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

Elements per page setting is discarded after editing an object #11372

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

Originally created by @vic-t on GitHub (Jul 13, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.3

Python Version

3.12

Steps to Reproduce

  1. Go into the "Interfaces" overview. This assumes that you have more than 25 interfaces.
  2. In the lower right corner, press the drop down "Per Page" and select that you wish to see 100 entries.
  3. Select two elements in this longer list, press "Edit Selected"
  4. Do the necessary changes and save.
  5. You're now being taken back to the "Interfaces" overview. You're back in the default view of 25 entries instead of 100.

Expected Behavior

I would expect that the setting remains active until I decide to leave the overview by explicitly navigating somewhere else.

Observed Behavior

As mentioned in "Steps to reproduce"

Originally created by @vic-t on GitHub (Jul 13, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.3 ### Python Version 3.12 ### Steps to Reproduce 1. Go into the "Interfaces" overview. This assumes that you have more than 25 interfaces. 2. In the lower right corner, press the drop down "Per Page" and select that you wish to see 100 entries. 3. Select two elements in this longer list, press "Edit Selected" 4. Do the necessary changes and save. 5. You're now being taken back to the "Interfaces" overview. You're back in the default view of 25 entries instead of 100. ### Expected Behavior I would expect that the setting remains active until I decide to leave the overview by explicitly navigating somewhere else. ### Observed Behavior As mentioned in "Steps to reproduce"
adam added the type: bugstatus: needs ownernetboxseverity: low labels 2025-12-29 21:44:20 +01:00
adam commented 2025-12-29 21:44:20 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jul 14, 2025):

I was very tempted to argue that this is intended behavior (in that it doesn't seem to have ever been considered) and that a feature request should be filed, if this should be added. However, while triaging this, I noticed that we're handling this differently for per_page values above the default as we are below the default--which is odd.

I will dig in to the more in a bit.

@jnovinger commented on GitHub (Jul 14, 2025): I was very tempted to argue that this is intended behavior (in that it doesn't seem to have ever been considered) and that a feature request should be filed, if this should be added. However, while triaging this, I noticed that we're handling this differently for `per_page` values above the default as we are below the default--which is odd. I will dig in to the more in a bit.
adam commented 2025-12-29 21:44:21 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Sep 12, 2025):

To elaborate a bit on my comment from July, there's definitely some inconsistent behavior. For instance:

  • If you select any of the predefined pagination sizes other than 100 (in my case, might be because of NetBox defaults or user preferences), then after a bulk edit, the pagination is reset back to 100.
  • If you manually set the per_page GET param to (it appears) anything else, like ?per_page=101, ?per_page=99, or even ?per_page=1, then the custom pagination is maintained after the bulk edit is completed.
  • Newly discovered just now, if you select one of the predefined pagination options, like say 500, after having set one manually like above, then you are redirected to the listing page and the previous manually set pagination number is used. In my case, I manually set ?per_page=101, did an edit, then selected 500 on the list page I was redirected to, then did another edit, and was redirected to the list page again which showed Showing 1-101 of 1613 and had ?per_page=101 in the URL.

So tl;dr, there's definitely a bug here. Opening it up for anyone that is interested. Apologies to all for letting it sit so long.

@jnovinger commented on GitHub (Sep 12, 2025): To elaborate a bit on my comment from July, there's definitely some inconsistent behavior. For instance: - If you select any of the predefined pagination sizes other than 100 (in my case, might be because of NetBox defaults or user preferences), then after a bulk edit, the pagination is reset back to 100. - If you manually set the `per_page` GET param to (it appears) anything else, like `?per_page=101`, `?per_page=99`, or even `?per_page=1`, then the custom pagination is maintained after the bulk edit is completed. - Newly discovered just now, if you select one of the predefined pagination options, like say `500`, _after_ having set one manually like above, then you are redirected to the listing page and the previous manually set pagination number is used. In my case, I manually set `?per_page=101`, did an edit, then selected `500` on the list page I was redirected to, then did another edit, and was redirected to the list page again which showed `Showing 1-101 of 1613` and had `?per_page=101` in the URL. So tl;dr, there's definitely a bug here. Opening it up for anyone that is interested. Apologies to all for letting it sit so long.
adam commented 2025-12-29 21:44:21 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 12, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 12, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
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 netbox severity: low status: needs owner type: bug
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#11372
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?