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

UX Enhancement: Assigning existing IP to interface #9244

New Issue
Open
opened 2025-12-29 20:47:26 +01:00 by adam · 7 comments
adam commented 2025-12-29 20:47:26 +01:00
Owner
Copy Link

Originally created by @kotso on GitHub (Feb 14, 2024).

NetBox version

v.3.7.2

Feature type

New functionality

Proposed functionality

When adding existing IP to interface, after clicking add icon, you have option to search for IP/VRF to find desired IP, in list of found IP's you have only option to navigate to IP edit page and set interface from there.

So it's even easier to just look for IP and set interface instead of navigating to interface page and clicking add.

I suggest that list of found IP addresses should just have button "Assign" that would assign them to interface we are currently editing.

Use case

current flow is IMHO not logical, as after finding address you are starting same assign operation from scratch.

Database changes

No database change required

External dependencies

No response

Originally created by @kotso on GitHub (Feb 14, 2024). ### NetBox version v.3.7.2 ### Feature type New functionality ### Proposed functionality When adding existing IP to interface, after clicking add icon, you have option to search for IP/VRF to find desired IP, in list of found IP's you have only option to navigate to IP edit page and set interface from there. So it's even easier to just look for IP and set interface instead of navigating to interface page and clicking add. I suggest that list of found IP addresses should just have button "Assign" that would assign them to interface we are currently editing. ### Use case current flow is IMHO not logical, as after finding address you are starting same assign operation from scratch. ### Database changes No database change required ### External dependencies _No response_
adam added the type: featurecomplexity: mediumnetboxstatus: backlogtopic: UI/UX labels 2025-12-29 20:47:26 +01:00
adam commented 2025-12-29 20:47:27 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Feb 14, 2024):

On the "Assign IP" tab, after you search for an existing IP address, if you click on the link in one of the search results, it does take you to the edit page for that IP, but it also assigns the interface that you were on. Sure, it's one extra click at that point to click on the "Save" button, but I find that I often need to change an attribute on the IP anyway, like changing the status from Reserved to Active, so it actually saves time in the long run.

@sleepinggenius2 commented on GitHub (Feb 14, 2024): On the "Assign IP" tab, after you search for an existing IP address, if you click on the link in one of the search results, it does take you to the edit page for that IP, but it also assigns the interface that you were on. Sure, it's one extra click at that point to click on the "Save" button, but I find that I often need to change an attribute on the IP anyway, like changing the status from Reserved to Active, so it actually saves time in the long run.
adam commented 2025-12-29 20:47:27 +01:00
Author
Owner
Copy Link

@rkiss commented on GitHub (Feb 16, 2024):

I was about to propose the same enhancement. I would go a bit further than the original ask and add a popup with two actions inside: "Assign" and "Assign and make primary". When selected it shall just do that, no question ask, and then go back to the corresponding interfaces tab of the device.
If the IP is already assigned to something else it should ask for a confirmation perhaps.
image

@rkiss commented on GitHub (Feb 16, 2024): I was about to propose the same enhancement. I would go a bit further than the original ask and add a popup with two actions inside: "Assign" and "Assign and make primary". When selected it shall just do that, no question ask, and then go back to the corresponding interfaces tab of the device. If the IP is already assigned to something else it should ask for a confirmation perhaps. ![image](https://github.com/netbox-community/netbox/assets/5818049/cb072a94-2cef-441a-aad6-be134b452d94)
adam commented 2025-12-29 20:47:27 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Feb 17, 2024):

I think there is some confusion about the process here. You should be clicking on the IP link over on the left, like where it says 10.241.168.1/23 or 10.241.168.10/23 in your screenshot. That will drop you into the edit screen for that IP with the selected interface assignment pre-populated. Then you just need to hit "Save" or make any other changes you need first, like selecting "Make this the primary IP for the device/VM", as requested, or changing the status from Reserved to Active. It will then send you back to the interfaces list for the device where you came from. It sounds like the existing functionality is already sufficient to meet all the requested feature enhancements.

@sleepinggenius2 commented on GitHub (Feb 17, 2024): I think there is some confusion about the process here. You should be clicking on the IP link over on the left, like where it says 10.241.168.1/23 or 10.241.168.10/23 in your screenshot. That will drop you into the edit screen for that IP **with the selected interface assignment pre-populated**. Then you just need to hit "Save" or make any other changes you need first, like selecting "Make this the primary IP for the device/VM", as requested, or changing the status from Reserved to Active. It will then send you back to the interfaces list for the device where you came from. It sounds like the existing functionality is already sufficient to meet all the requested feature enhancements.
adam commented 2025-12-29 20:47:27 +01:00
Author
Owner
Copy Link

@rkiss commented on GitHub (Feb 18, 2024):

I don't think that there is any confusion here. What you are describing is what we are all doing. The proposal is to make the process slightly faster, more streamlined.
I found that while working with Netbox there are many things where the number of clicks and waits for pages to load can be reduced if the right actions are available at a higher level. This is one of them.

@rkiss commented on GitHub (Feb 18, 2024): I don't think that there is any confusion here. What you are describing is what we are all doing. The proposal is to make the process slightly faster, more streamlined. I found that while working with Netbox there are many things where the number of clicks and waits for pages to load can be reduced if the right actions are available at a higher level. This is one of them.
adam commented 2025-12-29 20:47:27 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Feb 19, 2024):

current flow is IMHO not logical, as after finding address you are starting same assign operation from scratch.

While you may be following the correct process, the way that the use case above from the original feature request was written, it does not sound like that was the process that OP was following, but instead clicking the yellow edit button. Therefore, that is what I was basing my comments on. If your objective is to add a feature to reduce the one extra page load and click from how it is today, then that seems like a different use case than the feature request proposed here.

As an aside, we would never use such a feature in our instance, as our business process requires a number of things to be done with an IP address between reservation and assignment, like changing the status and generally validating things like the role and tenant, so the current process already meets our needs very well.

@sleepinggenius2 commented on GitHub (Feb 19, 2024): > current flow is IMHO not logical, as after finding address you are starting same assign operation from scratch. While you may be following the correct process, the way that the use case above from the original feature request was written, it does not sound like that was the process that OP was following, but instead clicking the yellow edit button. Therefore, that is what I was basing my comments on. If your objective is to add a feature to reduce the one extra page load and click from how it is today, then that seems like a different use case than the feature request proposed here. As an aside, we would never use such a feature in our instance, as our business process requires a number of things to be done with an IP address between reservation and assignment, like changing the status and generally validating things like the role and tenant, so the current process already meets our needs very well.
adam commented 2025-12-29 20:47:28 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 4, 2024):

Thanks for surfacing this UX gap. This kind of "papercut" struggle really adds up, and we could address it with a modest effort. I'm marking this issue needs owner; if you're interested in working it to a PR, please comment and somebody will assign it to you. Otherwise anybody with the right skills and spare working capacity can pick it up.

@jeffgdotorg commented on GitHub (Apr 4, 2024): Thanks for surfacing this UX gap. This kind of "papercut" struggle really adds up, and we could address it with a modest effort. I'm marking this issue `needs owner`; if you're interested in working it to a PR, please comment and somebody will assign it to you. Otherwise anybody with the right skills and spare working capacity can pick it up.
adam commented 2025-12-29 20:47:28 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 21, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 21, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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 complexity: medium netbox status: backlog topic: UI/UX 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#9244
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?