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

Add Pagination to Provider Detail View #2777

New Issue
Closed
opened 2025-12-29 18:22:04 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:22:04 +01:00
Owner
Copy Link

Originally created by @tyler-8 on GitHub (Aug 5, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.5.13

Proposed Functionality

Similar to https://github.com/netbox-community/netbox/issues/3314, the provider detail circuit listing would benefit from pagination when the object count is higher than a few hundred entries.

Edit: Same goes for IP Address detail page (Related and Duplicate IPs) (/ipam/ip-addresses/<id>/)

Use Case

When viewing Providers (e.g., /circuits/providers/att/) with a high number of circuits, the page loads very slow (and performs a larger DB query). Adding pagination will reduce the load on the webserver and the DB.

Edit: Same goes for IP Address detail page (Related and Duplicate IPs) (/ipam/ip-addresses/<id>/)

Database Changes

NA

External Dependencies

NA

Originally created by @tyler-8 on GitHub (Aug 5, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.8 <!-- Example: 3.5.4 --> * NetBox version: 2.5.13 <!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Similar to https://github.com/netbox-community/netbox/issues/3314, the provider detail circuit listing would benefit from pagination when the object count is higher than a few hundred entries. Edit: Same goes for IP Address detail page (Related and Duplicate IPs) (`/ipam/ip-addresses/<id>/`) <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When viewing Providers (e.g., `/circuits/providers/att/`) with a high number of circuits, the page loads very slow (and performs a larger DB query). Adding pagination will reduce the load on the webserver and the DB. Edit: Same goes for IP Address detail page (Related and Duplicate IPs) (`/ipam/ip-addresses/<id>/`) <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes NA <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies NA
adam added the status: acceptedtype: feature labels 2025-12-29 18:22:04 +01:00
adam closed this issue 2025-12-29 18:22:04 +01:00
adam commented 2025-12-29 18:22:04 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Aug 15, 2019):

Title needs to be changed to reflect the IP address detail page to be covered in this too.

@tyler-8 commented on GitHub (Aug 15, 2019): Title needs to be changed to reflect the IP address detail page to be covered in this too.
adam commented 2025-12-29 18:22:05 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Aug 26, 2019):

I think in this framework a global pagination should be introduced for all possible tables that exist as APPS in Netbox.

@tb-killa commented on GitHub (Aug 26, 2019): I think in this framework a global pagination should be introduced for all possible tables that exist as APPS in Netbox.
adam commented 2025-12-29 18:22:05 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Aug 26, 2019):

I think in this framework a global pagination should be introduced for all possible tables that exist as APPS in Netbox.

The project is already using https://github.com/jieter/django-tables2 to do just that - just needs to be enabled for the pages in question.

@tyler-8 commented on GitHub (Aug 26, 2019): > I think in this framework a global pagination should be introduced for all possible tables that exist as APPS in Netbox. The project is already using https://github.com/jieter/django-tables2 to do just that - just needs to be enabled for the pages in question.
adam commented 2025-12-29 18:22:05 +01:00
Author
Owner
Copy Link

@shuichiro-makigaki commented on GitHub (Sep 17, 2019):

Regarding "Related IP Address" table in the IP Address view, it becomes too heavy to load when the related IP address list is big. It is because the table does not have pagination feature (all items are listed on one page even if the list size is >9999...).

I think it is challenging to enable pagination on the table only because it is implemented as one of the subpanels on this page. Moving to a separate tab is easier in terms of implementation.

@shuichiro-makigaki commented on GitHub (Sep 17, 2019): Regarding "Related IP Address" table in the IP Address view, it becomes too heavy to load when the related IP address list is big. It is because the table does not have pagination feature (all items are listed on one page even if the list size is >9999...). I think it is challenging to enable pagination on the table only because it is implemented as one of the subpanels on this page. Moving to a separate tab is easier in terms of implementation.
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#2777
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?