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 Site field to Cables page #2822

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

Originally created by @ctrusler on GitHub (Aug 22, 2019).

Environment

currently running NetBox version: 2.6.1

Proposed Functionality

Add a column on the cables page to see what site the cables are in. Also add it to the search for the cables page

Use Case

we only keep cable numbers specific per site and not global.

today we can filter cables by color, type, and status. when trying to find the next available number for a specific type of cable in a specific site it would be easier if we could also filter by site.

Database Changes

Originally created by @ctrusler on GitHub (Aug 22, 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 currently running NetBox version: 2.6.1 ### Proposed Functionality Add a column on the cables page to see what site the cables are in. Also add it to the search for the cables page ### Use Case we only keep cable numbers specific per site and not global. today we can filter cables by color, type, and status. when trying to find the next available number for a specific type of cable in a specific site it would be easier if we could also filter by site. ### Database Changes
adam added the status: duplicate label 2025-12-29 18:22:28 +01:00
adam closed this issue 2025-12-29 18:22:28 +01:00
adam commented 2025-12-29 18:22:29 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Aug 29, 2019):

How would you handle the case of a cable connection that spans sites?

@lampwins commented on GitHub (Aug 29, 2019): How would you handle the case of a cable connection that spans sites?
adam commented 2025-12-29 18:22:29 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Sep 5, 2019):

I think the FR is to be understood as follows:

Display the site on each side of the cable connection, parallel to the racks.

Thus the respective endpoint can be referred directly to the site.

The filter could be difficult.
This need some more input how does should work.

@tb-killa commented on GitHub (Sep 5, 2019): I think the FR is to be understood as follows: Display the site on each side of the cable connection, parallel to the racks. Thus the respective endpoint can be referred directly to the site. The filter could be difficult. This need some more input how does should work.
adam commented 2025-12-29 18:22:29 +01:00
Author
Owner
Copy Link

@ctrusler commented on GitHub (Sep 6, 2019):

since cables themselves don't have a site it would need to reference the site the device/ports it connects to are in.

After looking at it more, I thought it would be an quick and easy lookup but it won't be that simple. I don't think patch ports have a site label for them so it would also need to check the parent patch panel for that also.

@ctrusler commented on GitHub (Sep 6, 2019): since cables themselves don't have a site it would need to reference the site the device/ports it connects to are in. After looking at it more, I thought it would be an quick and easy lookup but it won't be that simple. I don't think patch ports have a site label for them so it would also need to check the parent patch panel for that also.
adam commented 2025-12-29 18:22:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2019):

Covered by #3259

@jeremystretch commented on GitHub (Sep 26, 2019): Covered by #3259
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: duplicate
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#2822
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?