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

Missing (sub)parent location of device in the cable trace #7769

New Issue
Closed
opened 2025-12-29 20:27:59 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:27:59 +01:00
Owner
Copy Link

Originally created by @mbalcaen on GitHub (Mar 17, 2023).

NetBox version

v3.4.5

Python version

3.8

Steps to Reproduce

Screenshot 2023-03-17 12 30 37

Expected Behavior

I have a device VIC-V2-AP-LK in location "Leraarskamer".
"Leraarskamer" is a sublocation of "Floor 0".
"Floor 0" is a sublocation of the parent "Site Vichte V2".

When I do a cable trace I see only "Site Vichte V2" and "Leraarskamer", no sublocation "Floor 0".

Observed Behavior

Site Viceh V2 / Leeraarskamer.
I would like to see "Site Vichte V2 / Floor 0 / Leraarskamer".

Originally created by @mbalcaen on GitHub (Mar 17, 2023). ### NetBox version v3.4.5 ### Python version 3.8 ### Steps to Reproduce ![Screenshot 2023-03-17 12 30 37](https://user-images.githubusercontent.com/1210283/225894037-749edb80-50c7-4c98-9488-f17f3bd74a4a.png) ### Expected Behavior I have a device VIC-V2-AP-LK in location "Leraarskamer". "Leraarskamer" is a sublocation of "Floor 0". "Floor 0" is a sublocation of the parent "Site Vichte V2". When I do a cable trace I see only "Site Vichte V2" and "Leraarskamer", no sublocation "Floor 0". ### Observed Behavior Site Viceh V2 / Leeraarskamer. I would like to see "Site Vichte V2 / Floor 0 / Leraarskamer".
adam closed this issue 2025-12-29 20:27:59 +01:00
adam commented 2025-12-29 20:27:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2023):

This is expected behavior: Only the location to which the device is directly assigned is listed. Otherwise, the text could easily overflow the allotted space. (Consider a scenario with three or four levels of nested locations.)

You're welcome to submit a feature request proposing this change, but it would need to include a solution for handling deep hierarchies.

@jeremystretch commented on GitHub (Apr 4, 2023): This is expected behavior: Only the location to which the device is directly assigned is listed. Otherwise, the text could easily overflow the allotted space. (Consider a scenario with three or four levels of nested locations.) You're welcome to submit a feature request proposing this change, but it would need to include a solution for handling deep hierarchies.
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
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#7769
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?