starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Filter Devices dropdown in Connect view #2976

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

Originally created by @fknorn on GitHub (Oct 25, 2019).

Environment

  • Python version: Python version: 3.6.8
  • NetBox version: NetBox version: 2.6.5

Proposed Functionality

In the dcim/interfaces/xxx/connect view - filter the Device list based on type of connection to be made.

When clicking to connect an interface and selecting, say, Front port, the subsequent view's Device dropdown (in the B-side panel...) should be filtered so that only devices actually having front ports are listed.

Use Case

Well, when patching stuff, it is a bit annoying having to scroll or type in order to get to the desired device quick. For instance, there are usually only at most a handful of patch panels in a rack - but usually a whole bunch interfaces to be patched there. It would be much more convenient if the list was pre-filtered based on what kind of destination port is actually to be patched to...

Database Changes

Not an expert here, but I believe it's purely a change in the controller / view (?).

External Dependencies

none

Originally created by @fknorn on GitHub (Oct 25, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: Python version: 3.6.8 * NetBox version: NetBox version: 2.6.5 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality In the **dcim/interfaces/xxx/connect** view - filter the Device list based on type of connection to be made. When clicking to connect an interface and selecting, say, Front port, the subsequent view's Device dropdown (in the B-side panel...) should be filtered so that only devices actually having front ports are listed. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Well, when patching stuff, it is a bit annoying having to scroll or type in order to get to the desired device quick. For instance, there are usually only at most a handful of patch panels in a rack - but usually a whole bunch interfaces to be patched there. It would be much more convenient if the list was pre-filtered based on what kind of destination port is actually to be patched to... <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Not an expert here, but I believe it's purely a change in the controller / view (?). <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies none
adam closed this issue 2025-12-29 18:24:17 +01:00
adam commented 2025-12-29 18:24:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 25, 2019):

When clicking to connect an interface and selecting, say, Front port, the subsequent view's Device dropdown (in the B-side panel...) should be filtered so that only devices actually having front ports are listed.

I understand the motivation behind this, but I have to reject it because the confusion this would cause among novice users (which would manifest itself in the form of erroneous bug reports). Imagine the frustration you'd feel after creating a new device, then trying to create a connection from a different device to it and the new device doesn't appear in the list of available devices. With the current approach, it's immediately apparent that the device is there but is missing a suitable component to complete the connection.

@jeremystretch commented on GitHub (Oct 25, 2019): > When clicking to connect an interface and selecting, say, Front port, the subsequent view's Device dropdown (in the B-side panel...) should be filtered so that only devices actually having front ports are listed. I understand the motivation behind this, but I have to reject it because the confusion this would cause among novice users (which would manifest itself in the form of erroneous bug reports). Imagine the frustration you'd feel after creating a new device, then trying to create a connection from a different device to it and the new device doesn't appear in the list of available devices. With the current approach, it's immediately apparent that the device is there but is missing a suitable component to complete the connection.
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#2976
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?