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

Used Saved Filter not shown in UI when using ?filter= along with slug in URL #9824

New Issue
Closed
opened 2025-12-29 21:23:12 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:23:12 +01:00
Owner
Copy Link

Originally created by @mathieued on GitHub (Jun 10, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.10

Steps to Reproduce

  1. Create a Saved Filter object (e.g. for Sites)
  2. Use the created Saved Filter, with the appropriate object(s), using ?filter=<saved_filter_slug> in the URL (instead of ?filter_id=<saved_filter_id>)

Expected Behavior

I would expect to have the same behaviour as when using filter_id filter. This means seeing, just below the Results tab, the rounded-pill showing the selected Saved Filter, and also seeing it selected in the Filters tab.

Results Tab:
dummy_filter_expected_results_tab

Filters Tab:
dummy_filter_expected_filters_tab

Observed Behavior

When using ?filter=<saved_filter_slug>, even though the output is the expected one, and filter is well applied on the results, it is not shown in the UI as when using ?filter_id=<saved_filter_id>. We don't see anymore the rounded-pill indicating the used Saved Filter, neither the selection of the Saved Filter in the Filters tab.

Results Tab:
dummy_filter_observed_results_tab

Filters Tab:
dummy_filter_observed_filters_tab

Tested against self-hosted v3.7.1, but the same behaviour is observed on the online Netbox Demo in v4.0.5

Originally created by @mathieued on GitHub (Jun 10, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.1 ### Python Version 3.10 ### Steps to Reproduce 1. Create a **Saved Filter** object (e.g. for Sites) 2. Use the created **Saved Filter**, with the appropriate object(s), using `?filter=<saved_filter_slug>` in the URL (instead of `?filter_id=<saved_filter_id>`) ### Expected Behavior I would expect to have the same behaviour as when using `filter_id` filter. This means seeing, just below the **Results** tab, the rounded-pill showing the selected **Saved Filter**, and also seeing it selected in the **Filters** tab. **Results** Tab: ![dummy_filter_expected_results_tab](https://github.com/netbox-community/netbox/assets/60089071/7a8b770c-852f-4c64-afbc-027f4f87db4f) **Filters** Tab: ![dummy_filter_expected_filters_tab](https://github.com/netbox-community/netbox/assets/60089071/5fd6e64d-6e91-4c69-8e82-0f30ea3f35f7) ### Observed Behavior When using `?filter=<saved_filter_slug>`, even though the output is the expected one, and filter is well applied on the results, it is not shown in the UI as when using `?filter_id=<saved_filter_id>`. We don't see anymore the rounded-pill indicating the used **Saved Filter**, neither the selection of the **Saved Filter** in the **Filters** tab. Results Tab: ![dummy_filter_observed_results_tab](https://github.com/netbox-community/netbox/assets/60089071/749c64be-2ab4-4c8c-bab8-43cc0fb51731) Filters Tab: ![dummy_filter_observed_filters_tab](https://github.com/netbox-community/netbox/assets/60089071/7b4c808c-d686-454f-9555-ab63fac1e20c) Tested against self-hosted v3.7.1, but the same behaviour is observed on the online Netbox Demo in v4.0.5
adam added the type: bugstatus: blockednetboxseverity: low labels 2025-12-29 21:23:13 +01:00
adam closed this issue 2025-12-29 21:23:13 +01:00
adam commented 2025-12-29 21:23:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 17, 2024):

Not really a bug, as support for the slug form of the filter was never intended. At any rate, marking this as blocked by #15348.

@jeremystretch commented on GitHub (Jun 17, 2024): Not really a bug, as support for the slug form of the filter was never intended. At any rate, marking this as blocked by #15348.
adam commented 2025-12-29 21:23:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 14, 2025):

I believe this has been addressed under some other issue, as the described behavior works on NetBox v4.2.5.

@jeremystretch commented on GitHub (Mar 14, 2025): I believe this has been addressed under some other issue, as the described behavior works on NetBox v4.2.5.
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 netbox severity: low status: blocked type: bug
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#9824
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?