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 connecting cables quicker by pre-selecting B end Site and Rack #2709

New Issue
Closed
opened 2025-12-29 18:21:15 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:21:15 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Jun 29, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.6.1

Proposed Functionality

When creating a new cable, pre-select the Site and Rack of the B-end to be the Site and Rack of the A-end.

Anybody who wants to connect elsewhere would still have to select the correct Rack or Site/Rack anyway, so you might as well pre-select the most likely choice.

Use Case

In 2.6.1 there has been a regression in the UI, which means that connecting cables has become more tiresome.

After a data center move, I now have hundreds of cables to connect up. CSV import is a possibility, but due to heterogenous devices and interface names, selecting them from the available interfaces in the UI would make more sense.

However, the interface for adding a cable has changed between 2.5 and 2.6. Previously there were two tabs for the B end: under the first tab, you could just type the name of any device (or part of it) to select it. Under the second tab, you could choose to drill down via site and rack.

It appears the first option has been removed. Now what happens is:

  1. You click on the "Connect" button and you get a drop-down. I know I'm connecting to an Interface, so that's OK.

    image

  2. At the B side you must drill down via site, rack and device.

    image

  3. If you try to type into the "device" box without selecting Site/Rack, you are only allowed to choose unracked devices (across all sites). So you are forced to select Site and Rack (or just Rack) first, before typing in part of the target device name.

Under 2.5 it was going to be simple - working through the devices in rack X, I would have the name of the switch in rack X in my clipboard and just paste it in to the target device, then just have to select the interface. I can't do this now, without also selecting Site/Rack every time.

There are a bunch of ways the UI for connecting devices could be improved, but pre-selecting the Site and Rack would be minimally invasive and yet speed up the 80/20 case where connections are made within a rack (e.g. device to top-of-rack switch).

Another option would be that if the site and rack are unselecting, then typing into the Device field could search across all devices in the database. However I understand that is going to become less feasible when naming uniqueness rules are relaxed.

Database Changes

None

External Dependencies

None

Originally created by @candlerb on GitHub (Jun 29, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.6.1 ### Proposed Functionality When creating a new cable, pre-select the Site and Rack of the B-end to be the Site and Rack of the A-end. Anybody who wants to connect elsewhere would still have to select the correct Rack or Site/Rack anyway, so you might as well pre-select the most likely choice. ### Use Case In 2.6.1 there has been a regression in the UI, which means that connecting cables has become more tiresome. After a data center move, I now have hundreds of cables to connect up. CSV import is a possibility, but due to heterogenous devices and interface names, selecting them from the available interfaces in the UI would make more sense. However, the interface for adding a cable has changed between 2.5 and 2.6. Previously there were two tabs for the B end: under the first tab, you could just type the name of any device (or part of it) to select it. Under the second tab, you could choose to drill down via site and rack. It appears the first option has been removed. Now what happens is: 1. You click on the "Connect" button and you get a drop-down. I know I'm connecting to an Interface, so that's OK. ![image](https://user-images.githubusercontent.com/44789/60384113-c6467900-9a71-11e9-8e6f-714b81ea9459.png) 2. At the B side you must drill down via site, rack and device. ![image](https://user-images.githubusercontent.com/44789/60383941-158baa00-9a70-11e9-8d5d-c27461873e24.png) 3. If you try to type into the "device" box without selecting Site/Rack, you are only allowed to choose *unracked* devices (across all sites). So you are forced to select Site and Rack (or just Rack) first, before typing in part of the target device name. Under 2.5 it was going to be simple - working through the devices in rack X, I would have the name of the switch in rack X in my clipboard and just paste it in to the target device, then just have to select the interface. I can't do this now, without also selecting Site/Rack every time. There are a bunch of ways the UI for connecting devices could be improved, but pre-selecting the Site and Rack would be minimally invasive and yet speed up the 80/20 case where connections are made within a rack (e.g. device to top-of-rack switch). Another option would be that if the site and rack are unselecting, then typing into the Device field could search across all devices in the database. However I understand that is going to become less feasible when naming uniqueness rules are relaxed. ### Database Changes None ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:21:15 +01:00
adam closed this issue 2025-12-29 18:21:15 +01:00
adam commented 2025-12-29 18:21:15 +01:00
Author
Owner
Copy Link

@millijuna commented on GitHub (Oct 30, 2019):

For me, pre-populating the rack wouldn't be useful, but the site would be fine. The bigger thing for me would be to be able to search all of my devices without having to first select the site/rack. (my patch panels, for example, are named --patch.

@millijuna commented on GitHub (Oct 30, 2019): For me, pre-populating the rack wouldn't be useful, but the site would be fine. The bigger thing for me would be to be able to search all of my devices without having to first select the site/rack. (my patch panels, for example, are named <building>-<type>-patch.
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#2709
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?