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

Not Able to See ASNs Tab within ASN Range Without Being a Superuser #14195

Closed
markh0338 opened this issue Nov 6, 2023 · 1 comment · Fixed by #14229
Closed

Not Able to See ASNs Tab within ASN Range Without Being a Superuser #14195

markh0338 opened this issue Nov 6, 2023 · 1 comment · Fixed by #14229
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

@markh0338
Copy link

NetBox version

v3.6.4

Python version

3.8

Steps to Reproduce

  1. Within the IPAM module, create an ASN range that encompasses other/existing ASNs
  2. Open the ASN Range object as a user that does NOT have superuser permissions, but does have all other permissions

Expected Behavior

A user with ALL permissions (at least all IPAM permissions) should see an "ASNs" tab within the ASN Range object that lists all ASNs within the range.

Observed Behavior

Without superuser permissions, the "ASNs" tab is not shown.

@markh0338 markh0338 added the type: bug A confirmed report of unexpected behavior in the application label Nov 6, 2023
@markh0338 markh0338 changed the title Not Able to See ASN Tab within ASN Range Without Being a Superuser Not Able to See ASNs Tab within ASN Range Without Being a Superuser Nov 6, 2023
@abhi1693 abhi1693 added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Nov 9, 2023
@abhi1693 abhi1693 self-assigned this Nov 9, 2023
abhi1693 added a commit that referenced this issue Nov 9, 2023
@markh0338
Copy link
Author

Thank you @abhi1693

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 8, 2024
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

Successfully merging a pull request may close this issue.

2 participants