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

When connecting a cable, device search requires rack selection #3215

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

Originally created by @jeremystretch on GitHub (Jan 23, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7.2

Steps to Reproduce

  1. Navigate to a device which is not assigned to a rack
  2. Start to connect a cable to an unoccupied interface
  3. Search for the far end device, without selecting a rack

Expected Behavior

All devices within the selected remote site should be searchable

Observed Behavior

Only non-racked devices appear in the search results. Racked devices are included only if the appropriate rack is selected.

Originally created by @jeremystretch on GitHub (Jan 23, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.8 * NetBox version: 2.7.2 ### Steps to Reproduce 1. Navigate to a device which is not assigned to a rack 2. Start to connect a cable to an unoccupied interface 3. Search for the far end device, without selecting a rack ### Expected Behavior All devices within the selected remote site should be searchable ### Observed Behavior Only non-racked devices appear in the search results. Racked devices are included only if the appropriate rack is selected.
adam added the type: bugstatus: accepted labels 2025-12-29 18:26:48 +01:00
adam closed this issue 2025-12-29 18:26:48 +01:00
adam commented 2025-12-29 18:26:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 23, 2020):

This behavior is evident in other forms as well. For example, when assigning a device to a cluster, initially only non-grouped clusters are present in the cluster field's dropdown menu. The user must select a cluster group to view the clusters assigned to it: It is not possible to view all clusters (both grouped and non-grouped) at once.

@jeremystretch commented on GitHub (Jan 23, 2020): This behavior is evident in other forms as well. For example, when assigning a device to a cluster, initially only non-grouped clusters are present in the cluster field's dropdown menu. The user must select a cluster group to view the clusters assigned to it: It is not possible to view _all_ clusters (both grouped and non-grouped) at once.
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: bug
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#3215
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?