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

IPAddress Interface dropdown shows all interfaces, not only device ones #8377

New Issue
Closed
opened 2025-12-29 20:35:59 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:35:59 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Jul 28, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.5.6

Python version

3.8

Steps to Reproduce

  1. Create several devices with interfaces
  2. create an IP address
  3. assign the IP to an interface

This IP is now assigned to an interface of a device

  1. edit the IP adress
  2. open the dropdown of the 'interfaces
    image

Expected Behavior

The dropdown should only display the interfaces of the device it is assigned to.
If it needs to move to another device, then the 'filter' can be used.

That filter also is not aware of the device the IP/Interface belonged to
image
It should at least already show the 'Device' field with the device.

Observed Behavior

All interfaces of all devices are in the dropdown
The filter is not helping a lot, and needs a lot of clicking to get the proper filter setup (Click Filter, Check Device, Click devicefield, Type devicename, Click proper device, click to close the dropdown, click search)

Originally created by @PieterL75 on GitHub (Jul 28, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.5.6 ### Python version 3.8 ### Steps to Reproduce 1. Create several devices with interfaces 2. create an IP address 3. assign the IP to an interface This IP is now assigned to an interface of a device 1. edit the IP adress 2. open the dropdown of the 'interfaces ![image](https://github.com/netbox-community/netbox/assets/74899468/1333bd83-9029-4dac-a79c-10e63d4c21d4) ### Expected Behavior The dropdown should only display the interfaces of the device it is assigned to. If it needs to move to another device, then the 'filter' can be used. That filter also is not aware of the device the IP/Interface belonged to ![image](https://github.com/netbox-community/netbox/assets/74899468/470fbf94-582a-482e-b2b4-8bb150bb3f75) It should at least already show the 'Device' field with the device. ### Observed Behavior All interfaces of all devices are in the dropdown The filter is not helping a lot, and needs a lot of clicking to get the proper filter setup (Click Filter, Check Device, Click devicefield, Type devicename, Click proper device, click to close the dropdown, click search)
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:35:59 +01:00
adam closed this issue 2025-12-29 20:35:59 +01:00
adam commented 2025-12-29 20:35:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 28, 2023):

Once PR #13296 is merged. we can piggyback to fix this one too, at least the first part of it.

@DanSheps commented on GitHub (Jul 28, 2023): Once PR #13296 is merged. we can piggyback to fix this one too, at least the first part of it.
adam commented 2025-12-29 20:35:59 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Aug 3, 2023):

related: https://github.com/netbox-community/netbox/issues/12751

@ITJamie commented on GitHub (Aug 3, 2023): related: https://github.com/netbox-community/netbox/issues/12751
adam commented 2025-12-29 20:35:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 22, 2023):

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 (Nov 22, 2023): 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).
adam commented 2025-12-29 20:36:00 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Nov 29, 2023):

Once PR #13296 is merged. we can piggyback to fix this one too, at least the first part of it.

@DanSheps now that the above got merged is there anything blocking this?

@ITJamie commented on GitHub (Nov 29, 2023): > Once PR #13296 is merged. we can piggyback to fix this one too, at least the first part of it. @DanSheps now that the above got merged is there anything blocking this?
adam commented 2025-12-29 20:36:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2023):

Marking this as blocked by #12751 for now.

@jeremystretch commented on GitHub (Dec 14, 2023): Marking this as blocked by #12751 for now.
adam commented 2025-12-29 20:36:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 27, 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 (Mar 27, 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 severity: low 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#8377
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?