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

When creating a new prefix and selecting a site VLANs are not filtered #13721

Closed
patrickfnielsen opened this issue Sep 8, 2023 · 2 comments
Closed
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@patrickfnielsen
Copy link

patrickfnielsen commented Sep 8, 2023

NetBox version

v3.6.1

Python version

3.11

Steps to Reproduce

  • Create two new sites with the following names, and mark them active: site1 and site2
  • On both sites create the following VLANs:
    • VID: 10, Name: Test
    • VID: 20, Name: Test2
  • Create a new prefix
    • Any prefix will do
    • Select site1
    • Notice that when selecting VLAN's you can select VLAN's from both sites

Expected Behavior

Before the new selector widget was added VLANs would be filtered when you selected a site, that is not the case anymore. When you select a site all VLANs are still shown, and you have to use the new selector widget to select the site once again.

Observed Behavior

VLANs are not filtered, instead all VLANs are shown

@patrickfnielsen patrickfnielsen added the type: bug A confirmed report of unexpected behavior in the application label Sep 8, 2023
@jeremystretch
Copy link
Member

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Sep 8, 2023
@patrickfnielsen
Copy link
Author

I have updated the issue.

@jeremystretch jeremystretch removed the status: revisions needed This issue requires additional information to be actionable label Sep 11, 2023
@jeremystretch jeremystretch self-assigned this Sep 11, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Sep 11, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants