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

Add site/location selectors to interface assignment of "Add new IP address" #6529

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

Originally created by @dbbnrl on GitHub (Jun 2, 2022).

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

I believe this is a GUI-only proposal.

In the "Interface Assignment" section of the "Add a new IP address" screen, I propose adding the usual suite of region/sitegroup/site/location/etc selectors above the Device dropdown. This allows the user to narrow down the set of devices shown in the dropdown.

Use case

Currently I'm aware of two workflows for assigning IPs to interfaces:

  1. Via the device's interface list, by clicking on the plus icon and selecting "IP Address". This populates the device/interface for you, but the problem is that you need to already know what to type in the Address field. (It would be great if there was some kind of search/navigation facility here to help you select an address, but that's not in the scope of this proposal).
  2. Via e.g. selecting a Prefix, then "IP Addresses", then the "Add IP Address" button or clicking on an available address. This facilitates choosing a free address, but requires you to specify the Device. This is difficult when there are many devices; thus this proposal.

Database changes

No response

External dependencies

No response

Originally created by @dbbnrl on GitHub (Jun 2, 2022). ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality I believe this is a GUI-only proposal. In the "Interface Assignment" section of the "Add a new IP address" screen, I propose adding the usual suite of region/sitegroup/site/location/etc selectors above the Device dropdown. This allows the user to narrow down the set of devices shown in the dropdown. ### Use case Currently I'm aware of two workflows for assigning IPs to interfaces: 1. Via the device's interface list, by clicking on the plus icon and selecting "IP Address". This populates the device/interface for you, but the problem is that you need to already know what to type in the Address field. (It would be great if there was some kind of search/navigation facility here to help you select an address, but that's not in the scope of this proposal). 2. Via e.g. selecting a Prefix, then "IP Addresses", then the "Add IP Address" button or clicking on an available address. This facilitates choosing a free address, but requires you to specify the Device. This is difficult when there are many devices; thus this proposal. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:42:01 +01:00
adam closed this issue 2025-12-29 19:42:01 +01:00
adam commented 2025-12-29 19:42:02 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Jun 9, 2022):

A modal popup to search for a device might be a better option than adding all those fields to the edit/create view

@ITJamie commented on GitHub (Jun 9, 2022): A modal popup to search for a device might be a better option than adding all those fields to the edit/create view
adam commented 2025-12-29 19:42:02 +01:00
Author
Owner
Copy Link

@dbbnrl commented on GitHub (Jun 17, 2022):

Maybe so, but I was trying to propose something that would require minimal development.

@dbbnrl commented on GitHub (Jun 17, 2022): Maybe so, but I was trying to propose something that would require minimal development.
adam commented 2025-12-29 19:42:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 16, 2022):

A modal popup to search for a device might be a better option than adding all those fields to the edit/create view

#10054 was opened to capture this initiative, and will deliver a much smoother user experience. We should focus our efforts there rather than continuing to extend already cluttered forms with additional fields.

@jeremystretch commented on GitHub (Sep 16, 2022): > A modal popup to search for a device might be a better option than adding all those fields to the edit/create view #10054 was opened to capture this initiative, and will deliver a much smoother user experience. We should focus our efforts there rather than continuing to extend already cluttered forms with additional fields.
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#6529
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?