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

Make Cable Trace Views Configurable #10577

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

Originally created by @KaricAllegra on GitHub (Dec 17, 2024).

NetBox version

v4.1.7

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Currently, when using the "Trace Cable" functionality, the user is presented with a trace image that displays only specific fields on the cable. I propose that the user be able to select which fields are displayed.

Could a configurable view be enacted (like the one currently in place for tables)?

Use case

  • Create a cable and have certain tags associated to it, it would be beneficial to be able to "enable" them to be displayed.

  • Want to show a cable trace to a customer, but do not want to display the label.

  • Would like the NetBox ID field to be displayed when trying to write an API call.

Database changes

None

External dependencies

None

Originally created by @KaricAllegra on GitHub (Dec 17, 2024). ### NetBox version v4.1.7 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Currently, when using the "Trace Cable" functionality, the user is presented with a trace image that displays only specific fields on the cable. I propose that the user be able to select which fields are displayed. Could a configurable view be enacted (like the one currently in place for tables)? ### Use case - Create a cable and have certain tags associated to it, it would be beneficial to be able to "enable" them to be displayed. - Want to show a cable trace to a customer, but do not want to display the label. - Would like the NetBox ID field to be displayed when trying to write an API call. ### Database changes None ### External dependencies None
adam added the type: featurenetboxneeds milestonestatus: backlogcomplexity: high labels 2025-12-29 21:33:20 +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 complexity: high needs milestone netbox status: backlog 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#10577
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?