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

Show Location in Device Drop Down #10998

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

Originally created by @RobertArndtEllerhold on GitHub (Apr 8, 2025).

NetBox version

4.2.6

Feature type

Change to existing functionality

Proposed functionality

When creating or changing a cabling, the location of a device should also be displayed in the dropdown for the device so that devices with the same name at different locations can be recognized directly. The location should also be recognizable in the drop-down for the interface.

Device drop-down:
Image

Interface drop-down:
Image

Use case

If a company like ours has several locations (7), it is often the case that several devices have the same name. For example, there is a switch “sw-internal-1” in location "A" and also a switch “sw-internal-1” in location B. Since devices must have a unique name for each location, it is not necessary to name these devices differently, e.g. “sw-internal-1-A” and “sw-internal-1-B”, which would differ from the true names

When creating or changing a cabling, the end points of the cable must be selected. To do this, yout have to select the device and the interface, or only the interface. However, if there are several devices with the same name at different locations, as in our case, the devices/interfaces cannot be distinguished in the drop-down menu as only the name is displayed.

With the additional display of the location of a device in this drop-down menus, a device would be easier to identify and cabling would be much simpler.

Database changes

No response

External dependencies

No response

Originally created by @RobertArndtEllerhold on GitHub (Apr 8, 2025). ### NetBox version 4.2.6 ### Feature type Change to existing functionality ### Proposed functionality When creating or changing a cabling, the location of a device should also be displayed in the dropdown for the device so that devices with the same name at different locations can be recognized directly. The location should also be recognizable in the drop-down for the interface. **Device drop-down:** ![Image](https://github.com/user-attachments/assets/608fcf80-fd3d-4331-961a-73703d181e29) **Interface drop-down:** ![Image](https://github.com/user-attachments/assets/133fd1b0-6295-4a16-b5ea-37d99df6bdb6) ### Use case If a company like ours has several locations (7), it is often the case that several devices have the same name. For example, there is a switch “sw-internal-1” in location "A" and also a switch “sw-internal-1” in location B. Since devices must have a unique name for each location, it is not necessary to name these devices differently, e.g. “sw-internal-1-A” and “sw-internal-1-B”, which would differ from the true names When creating or changing a cabling, the end points of the cable must be selected. To do this, yout have to select the device and the interface, or only the interface. However, if there are several devices with the same name at different locations, as in our case, the devices/interfaces cannot be distinguished in the drop-down menu as only the name is displayed. With the additional display of the location of a device in this drop-down menus, a device would be easier to identify and cabling would be much simpler. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:38:58 +01:00
adam closed this issue 2025-12-29 21:38:58 +01:00
adam commented 2025-12-29 21:38:59 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Apr 8, 2025):

NetBox already provides a selector that filters devices based on attributes such as location; you’ll find it right next to the dropdown. The location isn’t shown by default in the dropdown because there are cases where sub-locations (such as “level 3”) exist in multiple parent locations. Using the selector ensures that you can quickly find the correct device and interface.

As a side note, it is standard practice to give devices globally unique names rather than merely unique names within a single location. Often, this is achieved by incorporating the location identifier into the device name.

@pheus commented on GitHub (Apr 8, 2025): NetBox already provides a selector that filters devices based on attributes such as location; you’ll find it right next to the dropdown. The location isn’t shown by default in the dropdown because there are cases where sub-locations (such as “level 3”) exist in multiple parent locations. Using the selector ensures that you can quickly find the correct device and interface. As a side note, it is standard practice to give devices globally unique names rather than merely unique names within a single location. Often, this is achieved by incorporating the location identifier into the device name.
adam commented 2025-12-29 21:38:59 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Apr 8, 2025):

Concurring with @pheus and also thinking that Location is not the only possibly helpful metadata that someone might want to add to the dropdown values (why not Site or Region? etc); I think this would muddy the waters more than help.

@bctiemann commented on GitHub (Apr 8, 2025): Concurring with @pheus and also thinking that Location is not the only possibly helpful metadata that someone might want to add to the dropdown values (why not Site or Region? etc); I think this would muddy the waters more than help.
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 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#10998
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?