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

Link to prefixes in Site view is wrong #18324

Closed
rodvand opened this issue Jan 7, 2025 · 0 comments · Fixed by #18326
Closed

Link to prefixes in Site view is wrong #18324

rodvand opened this issue Jan 7, 2025 · 0 comments · Fixed by #18326
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

@rodvand
Copy link
Contributor

rodvand commented Jan 7, 2025

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.2.0

Python Version

3.12

Steps to Reproduce

  1. Go to one of your many sites
  2. In the right hand side, click the link to prefixes

Expected Behavior

Only prefixes assigned to the site is shown.

Observed Behavior

The link on the right hand side is /ipam/prefixes/?_site_id=24 instead of /ipam/prefixes/?site_id=24 which results in absolutely all prefixes being displayed when you click the link.

@rodvand rodvand added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 7, 2025
@jeremystretch jeremystretch self-assigned this Jan 7, 2025
@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 and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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

Successfully merging a pull request may close this issue.

2 participants