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

Interface assignment does not offer device selection anymore #1350

New Issue
Closed
opened 2025-12-29 16:31:41 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:31:41 +01:00
Owner
Copy Link

Originally created by @jdecorniquet on GitHub (Oct 23, 2017).

###Issue type

[ ] Feature request
[X ] Bug report
[ ] Documentation

###Environment

Python version: 2.7..9
NetBox version: 2.2.2

###Description

Hello,

I must have missed something in the release notes but, we notice when editing an IP adresse assignement, on a device, we can't actually select another device (to change the assignement). See the screenshot below :

screen shot 2017-10-23 at 3 52 21 pm

We use to have the possibility to make Interface Assignement directly when adding an IP address, the below fields do not exist anymore :

screen shot 2017-10-23 at 3 57 36 pm

Looks like it's gone since 2.2.0, is it related to the Virtualization module and therefor, not a bug ?

Regards,

Originally created by @jdecorniquet on GitHub (Oct 23, 2017). ###Issue type [ ] Feature request [X ] Bug report [ ] Documentation ###Environment Python version: 2.7..9 NetBox version: 2.2.2 ###Description Hello, I must have missed something in the release notes but, we notice when editing an IP adresse assignement, on a device, we can't actually select another device (to change the assignement). See the screenshot below : <img width="788" alt="screen shot 2017-10-23 at 3 52 21 pm" src="https://user-images.githubusercontent.com/26890473/31910184-b7468f6c-b80a-11e7-9ea0-cc095bb0dcfc.png"> We use to have the possibility to make Interface Assignement directly when adding an IP address, the below fields do not exist anymore : <img width="788" alt="screen shot 2017-10-23 at 3 57 36 pm" src="https://user-images.githubusercontent.com/26890473/31910280-fa0c7b72-b80a-11e7-9c00-0bffbcb8b7d7.png"> Looks like it's gone since 2.2.0, is it related to the Virtualization module and therefor, not a bug ? Regards,
adam added the status: duplicate label 2025-12-29 16:31:41 +01:00
adam closed this issue 2025-12-29 16:31:41 +01:00
adam commented 2025-12-29 16:31:42 +01:00
Author
Owner
Copy Link

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

Duplicate of #1512

@jeremystretch commented on GitHub (Oct 23, 2017): Duplicate of #1512
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 status: duplicate
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#1350
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?