Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assigning an IP to a device interface is now overly cumbersome? #12669

Closed
mgob opened this issue May 19, 2023 · 3 comments
Closed

Assigning an IP to a device interface is now overly cumbersome? #12669

mgob opened this issue May 19, 2023 · 3 comments
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application

Comments

@mgob
Copy link

mgob commented May 19, 2023

NetBox version

v3.5.1

Python version

3.8

Steps to Reproduce

  1. Find an available IP address
  2. Click edit or Add
  3. Navigate to assgin to device, interfaces for ALL devices are listed by default but you have to open the enhanced search window to the right to get to search by device. This did not used to be the case.

Expected Behavior

Ability to filter by device FIRST before filtering by interface

Observed Behavior

Interfaces are listed without devices for assigning to a device.

Either this is a regression or a poor UI change that adds an unnecessary step to assigning an IP to a device interface. Alternatively I'm a moron and missed a settings change somewhere along the way to make this not the default behavior LOL.

IMG_0106

@mgob mgob added the type: bug A confirmed report of unexpected behavior in the application label May 19, 2023
@mgob
Copy link
Author

mgob commented May 19, 2023

It would appear this is related to #10757 ?

@jsenecal
Copy link
Contributor

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@jsenecal jsenecal added the status: revisions needed This issue requires additional information to be actionable label May 20, 2023
@mgob
Copy link
Author

mgob commented May 20, 2023

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

It’s very odd intended behavior if it truly is, I’ll open a feature request. I’ve got numerous user complaints over this change.

@mgob mgob closed this as completed May 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants