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

Query filters are removed when adding columns to table in list view #11784

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

Originally created by @rodvand on GitHub (Oct 27, 2025).

NetBox Edition

NetBox Community

NetBox Version

v4.4.4

Python Version

3.10

Steps to Reproduce

  1. Go to Devices
  2. Search for Akron
  3. Click Configure table and any column to the view

Expected Behavior

That the query filter (?q=Akron) persists, now with my newly added column in the view.

Observed Behavior

The query filter is gone and I have a list of all devices in the view.

Originally created by @rodvand on GitHub (Oct 27, 2025). ### NetBox Edition NetBox Community ### NetBox Version v4.4.4 ### Python Version 3.10 ### Steps to Reproduce 1. Go to Devices 2. Search for Akron 3. Click Configure table and any column to the view ### Expected Behavior That the query filter (?q=Akron) persists, now with my newly added column in the view. ### Observed Behavior The query filter is gone and I have a list of all devices in the view.
adam added the type: bugnetbox labels 2025-12-29 21:49:50 +01:00
adam closed this issue 2025-12-29 21:49:50 +01:00
adam commented 2025-12-29 21:49:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 27, 2025):

IMO this is to be expected, as the result of adding or removing columns is effectively a new view.

This change would be especially confusing when removing from display a column that is being used for filtering.

@jeremystretch commented on GitHub (Oct 27, 2025): IMO this is to be expected, as the result of adding or removing columns is effectively a new view. This change would be especially confusing when removing from display a column that is being used for filtering.
adam commented 2025-12-29 21:49:50 +01:00
Author
Owner
Copy Link

@rodvand commented on GitHub (Oct 27, 2025):

IMO this is to be expected, as the result of adding or removing columns is effectively a new view.

This change would be especially confusing when removing from display a column that is being used for filtering.

I guess I can only speak for myself, but I always find it a bit annoying to have to redo my original filter just because I wanted to add the rack position column to my view. Not gonna argue hard about it, just didn't think it was intentional.

@rodvand commented on GitHub (Oct 27, 2025): > IMO this is to be expected, as the result of adding or removing columns is effectively a new view. > > This change would be especially confusing when removing from display a column that is being used for filtering. I guess I can only speak for myself, but I always find it a bit annoying to have to redo my original filter just because I wanted to add the rack position column to my view. Not gonna argue hard about it, just didn't think it was intentional.
adam commented 2025-12-29 21:49:50 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 28, 2025):

As noted, the current behavior is intentional. However, you can work around this some in a couple of ways:

  1. Create saved table configs for different scenarios (e.g., "Basic view," "Detailed view with rack position")
  2. Save frequently-used searches like "Akron" as a saved filter
  3. Switch between saved configs and then make use of saved filters/searches

This way you only configure columns once, and your common searches are one click away.

That said, I personally agree with you. This behavior also surprised me the first time I encountered it. I will note that NetBox already provides dismissable filter pills so users can selectively remove filters if they get confusing results.

Since this is known and expected behavior by the maintainers, I'm closing this bug as not planned. However, if you'd like to resubmit this as a feature request to preserve query filters during table configuration, we'll certainly give it fair consideration. There may well be legitimate UX reasons why users expect their search context to persist during view customization.

@jnovinger commented on GitHub (Oct 28, 2025): As noted, the current behavior is intentional. However, you can work around this some in a couple of ways: 1. Create saved table configs for different scenarios (e.g., "Basic view," "Detailed view with rack position") 2. Save frequently-used searches like "Akron" as a saved filter 3. Switch between saved configs and then make use of saved filters/searches This way you only configure columns once, and your common searches are one click away. That said, I personally agree with you. This behavior also surprised me the first time I encountered it. I will note that NetBox already provides dismissable filter pills so users can selectively remove filters if they get confusing results. Since this is known and expected behavior by the maintainers, I'm closing this bug as not planned. However, if you'd like to resubmit this as a feature request to preserve query filters during table configuration, we'll certainly give it fair consideration. There may well be legitimate UX reasons why users expect their search context to persist during view customization.
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 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#11784
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?