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 filter to select cables by termination sites #2667

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

Originally created by @ajknv on GitHub (Jun 14, 2019).

Environment

  • Python version: 2.7.5
  • NetBox version: 2.5.13

Proposed Functionality

Would like to have the ability to list cables filtered by the site assigned to either or both of the termination endpoints.

Use Case

The goal is to be able to pull up inventories of all the equipment associated with a particular site. Currently there is no straightforward/convenient way to do this for cables.

Database Changes

None that I would expect.

External Dependencies

None.

Originally created by @ajknv on GitHub (Jun 14, 2019). ### Environment * Python version: 2.7.5 * NetBox version: 2.5.13 ### Proposed Functionality Would like to have the ability to list cables filtered by the site assigned to either or both of the termination endpoints. ### Use Case The goal is to be able to pull up inventories of all the equipment associated with a particular site. Currently there is no straightforward/convenient way to do this for cables. ### Database Changes None that I would expect. ### External Dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 18:21:01 +01:00
adam closed this issue 2025-12-29 18:21:01 +01:00
adam commented 2025-12-29 18:21:01 +01:00
Author
Owner
Copy Link

@coppit commented on GitHub (Jun 14, 2019):

The cables UI is not scalable. Consider 15 sites and 300 cables each. That's 4500 cables presented as pages in the UI. Because there's no substring matching for device name, one cannot use naming conventions to help filter down to a specific site.

I also find it odd that devices are listed in the "Stats" box for a site, but cables are not. If this feature is implemented, that could be rectified with a simple link with a "?site=foo" filter in the URL.

@coppit commented on GitHub (Jun 14, 2019): The cables UI is not scalable. Consider 15 sites and 300 cables each. That's 4500 cables presented as pages in the UI. Because there's no substring matching for device name, one cannot use naming conventions to help filter down to a specific site. I also find it odd that devices are listed in the "Stats" box for a site, but cables are not. If this feature is implemented, that could be rectified with a simple link with a "?site=foo" filter in the URL.
adam commented 2025-12-29 18:21:01 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Jul 10, 2019):

If adding filter cables by site, can we have filter by rack as well please!

@candlerb commented on GitHub (Jul 10, 2019): If adding filter cables by site, can we have filter by rack as well please!
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#2667
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?