starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Cannot filter sites by physical_address #8627

New Issue
Closed
opened 2025-12-29 20:39:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:39:05 +01:00
Owner
Copy Link

Originally created by @apm6 on GitHub (Sep 17, 2023).

NetBox version

3.1.5

Python version

3.10

Steps to Reproduce

'/dcim/sites?physical_address=test'

Expected Behavior

I would expect this filter to work since physical_address is a field in the site object.

Observed Behavior

The physical_address filter does not work and the api returns all sites. Using 'address' as the filter does not work either.

Originally created by @apm6 on GitHub (Sep 17, 2023). ### NetBox version 3.1.5 ### Python version 3.10 ### Steps to Reproduce '/dcim/sites?physical_address=test' ### Expected Behavior I would expect this filter to work since physical_address is a field in the site object. ### Observed Behavior The physical_address filter does not work and the api returns all sites. Using 'address' as the filter does not work either.
adam closed this issue 2025-12-29 20:39:05 +01:00
adam commented 2025-12-29 20:39:05 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Sep 17, 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.

I do not think this is a bug because even on the latest version (3.6.1), I do not see any filter on the site for physical address. You should rather raise this as a feature request. Moreover, I'd suggest to upgrade to the latest version if possible as the FR will be added for 3.6 if accepted.

@abhi1693 commented on GitHub (Sep 17, 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](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed. I do not think this is a bug because even on the latest version (3.6.1), I do not see any filter on the site for physical address. You should rather raise this as a feature request. Moreover, I'd suggest to upgrade to the latest version if possible as the FR will be added for 3.6 if accepted.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8627
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?