Accessing saved filters gives permissions error #7629

Closed
opened 2025-12-29 20:26:13 +01:00 by adam · 3 comments
Owner

Originally created by @FliesLikeABrick on GitHub (Feb 9, 2023).

NetBox version

v3.4.4

Python version

3.8

Steps to Reproduce

Database was upgraded from 2.x to current over time, not a fresh install. In a clean install of netbox (or in a brand new containerized environment and database), this issue is not seen
Browse to prefixes
Switch to "Filters" tab
Click on "Saved Filter"
Observe error: Error Fetching Options for field 'filter_id'
You do not have permission to perform this action

Expected Behavior

User should be able to access or define saved filters, or in our case observe that none exist yet
-- or --
NetBox documentation should be improved to explain the permissions that need to be granted to make this feature work after an upgrade that provides the new feature.

Observed Behavior

Error Fetching Options for field 'filter_id'

You do not have permission to perform this action

Originally created by @FliesLikeABrick on GitHub (Feb 9, 2023). ### NetBox version v3.4.4 ### Python version 3.8 ### Steps to Reproduce Database was upgraded from 2.x to current over time, not a fresh install. In a clean install of netbox (or in a brand new containerized environment and database), this issue is not seen Browse to prefixes Switch to "Filters" tab Click on "Saved Filter" Observe error: Error Fetching Options for field 'filter_id' You do not have permission to perform this action ### Expected Behavior User should be able to access or define saved filters, or in our case observe that none exist yet -- or -- NetBox documentation should be improved to explain the permissions that need to be granted to make this feature work after an upgrade that provides the new feature. ### Observed Behavior Error Fetching Options for field 'filter_id' You do not have permission to perform this action
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:26:13 +01:00
adam closed this issue 2025-12-29 20:26:13 +01:00
Author
Owner

@FliesLikeABrick commented on GitHub (Feb 9, 2023):

I originally posted this as a discussion at https://github.com/netbox-community/netbox/discussions/11654

@FliesLikeABrick commented on GitHub (Feb 9, 2023): I originally posted this as a discussion at https://github.com/netbox-community/netbox/discussions/11654
Author
Owner

@jeremystretch commented on GitHub (Feb 9, 2023):

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 commented on GitHub (Feb 9, 2023): 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.
Author
Owner

@FliesLikeABrick commented on GitHub (Feb 9, 2023):

@jeremystretch thank you for the reply. I will resubmit a new issue with a narrower scope - this was written originally seeking guidance that would help me narrow this down to an actionable problem request, but I think I can phrase a new issue in a way that achieves similar goals.

@FliesLikeABrick commented on GitHub (Feb 9, 2023): @jeremystretch thank you for the reply. I will resubmit a new issue with a narrower scope - this was written originally seeking guidance that would help me narrow this down to an actionable problem request, but I think I can phrase a new issue in a way that achieves similar goals.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7629