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 Cable Length to Connections/Cables Filter #5881

New Issue
Closed
opened 2025-12-29 19:33:49 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:33:49 +01:00
Owner
Copy Link

Originally created by @sthierolf on GitHub (Jan 5, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.3

Feature type

Change to existing functionality

Proposed functionality

In Connections -> Cables -> Filters I would like to ask to extend the filter function with cable length.

Currently the Filter supports:
Site, Rack, Device
Type, Status, Color

An additional filter for the cable length would be helpful as described in the use case.

Use case

The use case is to filter out the cables not only by type, status or color but also by length to ease the creation of a BOM (bill of material process).

A typical BOM might list type, color, length and qty and might be in a spreadsheet handed over to a supplier.

Cat6A | Grey | 2 meters -> 50
Cat6A | Grey | 1 meters -> 50
Cat6A | Blue | 2 meters -> 20
OM4 | Aqua | 1 meters -> 10

By adding the length as a Filter we can transfer the qty (result of filter) in a BOM spreadsheet easily because we don't need to count every single cable in the result.

Database changes

No response

External dependencies

No response

Originally created by @sthierolf on GitHub (Jan 5, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.3 ### Feature type Change to existing functionality ### Proposed functionality In **Connections** -> **Cables** -> **Filters** I would like to ask to extend the filter function with cable **length**. Currently the Filter supports: Site, Rack, Device Type, Status, Color An additional filter for the cable length would be helpful as described in the use case. ### Use case The use case is to filter out the cables not only by type, status or color but also by length to ease the creation of a BOM (bill of material process). A typical BOM might list type, color, length and qty and might be in a spreadsheet handed over to a supplier. Cat6A | Grey | 2 meters -> 50 Cat6A | Grey | 1 meters -> 50 Cat6A | Blue | 2 meters -> 20 OM4 | Aqua | 1 meters -> 10 By adding the length as a **Filter** we can transfer the qty (result of filter) in a BOM spreadsheet easily because we don't need to count every single cable in the result. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:33:49 +01:00
adam closed this issue 2025-12-29 19:33:49 +01:00
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#5881
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?