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

Filter suggestions based on device "content" #1336

New Issue
Closed
opened 2025-12-29 16:31:34 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:31:34 +01:00
Owner
Copy Link

Originally created by @AnythingOverIP on GitHub (Oct 19, 2017).

Issue type

[ x ] Feature request

Environment

  • Python version: 3.5.4
  • NetBox version: 2.2.1

Description

When connecting a device, let's say a Server to a PDU, using the Search capability, devices returned in suggestions are all showing. It would be interesting to filter them to remove those who have no corresponding connectivity declared (ie: if a device has no power port, it should not show up in the suggestion list when connecting a power device... Same logic should then would be applied for networking and console.

A similar scenario would be in a page like "Add a new device", where all declared manufacturers would show up even if there are no Device Type created for some of the manufacturers. It would make the interface less loaded and easier to use if non relevant information was filtered.

Another scenario would apply to us, but I'm not sure if this would apply by default is that a Device type categorized as "Child" should not be suggested when adding devices to a rack.

Originally created by @AnythingOverIP on GitHub (Oct 19, 2017). ### Issue type [ x ] Feature request <!-- Requesting the implementation of a new feature --> ### Environment * Python version: 3.5.4 * NetBox version: 2.2.1 ### Description When connecting a device, let's say a Server to a PDU, using the Search capability, devices returned in suggestions are all showing. It would be interesting to filter them to remove those who have no corresponding connectivity declared (ie: if a device has no power port, it should not show up in the suggestion list when connecting a power device... Same logic should then would be applied for networking and console. A similar scenario would be in a page like "Add a new device", where all declared manufacturers would show up even if there are no Device Type created for some of the manufacturers. It would make the interface less loaded and easier to use if non relevant information was filtered. Another scenario would apply to us, but I'm not sure if this would apply by default is that a Device type categorized as "Child" should not be suggested when adding devices to a rack.
adam closed this issue 2025-12-29 16:31:34 +01:00
adam commented 2025-12-29 16:31:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 26, 2017):

This could result in very confusing behavior. We don't want to omit objects from a list unless the user knows why they're being omitted, and we don't have a way of expressing that when populating a selection field. For instance, if a user is expecting to find a certain device which has been silently omitted because it's missing a particular component, they're left wondering why the device isn't showing up. The more transparent approach is to allow them to select the device, and quickly realize that it's missing a particular component, which is easily resolved.

@jeremystretch commented on GitHub (Oct 26, 2017): This could result in very confusing behavior. We don't want to omit objects from a list unless the user knows why they're being omitted, and we don't have a way of expressing that when populating a selection field. For instance, if a user is expecting to find a certain device which has been silently omitted because it's missing a particular component, they're left wondering why the device isn't showing up. The more transparent approach is to allow them to select the device, and quickly realize that it's missing a particular component, which is easily resolved.
adam commented 2025-12-29 16:31:34 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Oct 30, 2017):

Based on the logic applied when you try to assign a child device to a device bay where only suitable devices are being showed (Child devices must first be created and assigned to the site/rack of the parent device.), I would say this feature request would provide a more coherent than confusing behavior.

Having no listing filtering provide a crowded interface that can lead to misselection by the user especially when the device nomenclature is not ideal...

I have the feeling the device definition (from the device types definition & modification) should drive the whole behavior. If it's not there in the list, the user can always go back to the device page and ensure it has the proper connection definitions instead of being proposed superfluous choices...

Could this "filtering" be proposed as an on/off option if we cannot convince everybody? :)

@AnythingOverIP commented on GitHub (Oct 30, 2017): Based on the logic applied when you try to assign a child device to a device bay where only suitable devices are being showed (Child devices must first be created and assigned to the site/rack of the parent device.), I would say this feature request would provide a more coherent than confusing behavior. Having no listing filtering provide a crowded interface that can lead to misselection by the user especially when the device nomenclature is not ideal... I have the feeling the device definition (from the device types definition & modification) should drive the whole behavior. If it's not there in the list, the user can always go back to the device page and ensure it has the proper connection definitions instead of being proposed superfluous choices... Could this "filtering" be proposed as an on/off option if we cannot convince everybody? :)
adam commented 2025-12-29 16:31:35 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Dec 13, 2017):

@jeremystretch , based on my last comment can this be reevaluated?

@AnythingOverIP commented on GitHub (Dec 13, 2017): @jeremystretch , based on my last comment can this be reevaluated?
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#1336
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?