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

Changing table config should not change filter #11232

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

Originally created by @llamafilm on GitHub (May 29, 2025).

NetBox version

v4.3.1

Feature type

Change to existing functionality

Proposed functionality

When applying a saved table config, the current filter should be preserved. For example, if I'm at URL
/dcim/interfaces/?site_id=329&device_role_id__n=15 and I apply a saved table config, I would expect to be at URL /dcim/interfaces/?site_id=329&device_role_id__n=15&tableconfig_id=1.

But instead, it takes me to /dcim/interfaces/?tableconfig_id=1 with no filter.

Conversely, if you select a table config first, then select a saved filter, that also removes tableconfig_id from the URL. The selected table config remains active for the current session, but I think it would be a problem if you try to share the URL with another user or bookmark it.

Use case

Creating a filter set from the webpage takes some time to get it right, so it's very annoying to lose that work. My workaround is to copy/paste the URL query string.

Database changes

No response

External dependencies

No response

Originally created by @llamafilm on GitHub (May 29, 2025). ### NetBox version v4.3.1 ### Feature type Change to existing functionality ### Proposed functionality When applying a saved table config, the current filter should be preserved. For example, if I'm at URL `/dcim/interfaces/?site_id=329&device_role_id__n=15` and I apply a saved table config, I would expect to be at URL `/dcim/interfaces/?site_id=329&device_role_id__n=15&tableconfig_id=1`. But instead, it takes me to `/dcim/interfaces/?tableconfig_id=1` with no filter. Conversely, if you select a table config first, then select a saved filter, that also removes `tableconfig_id` from the URL. The selected table config remains active for the current session, but I think it would be a problem if you try to share the URL with another user or bookmark it. ### Use case Creating a filter set from the webpage takes some time to get it right, so it's very annoying to lose that work. My workaround is to copy/paste the URL query string. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:42:15 +01:00
adam closed this issue 2025-12-29 21:42:15 +01:00
adam commented 2025-12-29 21:42:16 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 29, 2025):

The problem here is if you are filtering on a column and the saved configuration does not have that column it can get very confusing for the user.

@arthanson commented on GitHub (May 29, 2025): The problem here is if you are filtering on a column and the saved configuration does not have that column it can get very confusing for the user.
adam commented 2025-12-29 21:42:16 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (May 29, 2025):

Why would that be confusing? It's often a good idea to filter on a column which is not visible. For example, say I want to see Devices from one particular Site. Then the Site column would be the same for every row in the table, which is a waste of space. I generally prefer to hide any columns which are identical for all results.

I was excited about the new saved table config feature in 4.3 but if you have to copy/paste URL query strings every time, that's too complicated for most users.

@llamafilm commented on GitHub (May 29, 2025): Why would that be confusing? It's often a good idea to filter on a column which is not visible. For example, say I want to see Devices from one particular Site. Then the Site column would be the same for every row in the table, which is a waste of space. I generally prefer to hide any columns which are identical for all results. I was excited about the new saved table config feature in 4.3 but if you have to copy/paste URL query strings every time, that's too complicated for most users.
adam commented 2025-12-29 21:42:16 +01:00
Author
Owner
Copy Link

@peterbaumert commented on GitHub (May 30, 2025):

I understand the concern about filtered columns being hidden by a saved table config—it’s a fair point.

However, from a user perspective, it feels unintuitive that simply changing the table column configuration also removes the active filters. Filtering and choosing which columns to display seem like two separate actions, so it’s unexpected that one affects the other in this way.

I’d expect the filters to stay active regardless of which columns are currently visible. Losing filter state just by switching a saved table config can be frustrating, especially when a lot of time was spent setting up those filters.

Even if the filtered column is hidden, the filtering is still meaningful and often necessary—having the ability to preserve it, even with a subtle warning or indicator, would greatly improve the UX.

@peterbaumert commented on GitHub (May 30, 2025): I understand the concern about filtered columns being hidden by a saved table config—it’s a fair point. However, from a user perspective, it feels unintuitive that simply changing the table column configuration also removes the active filters. Filtering and choosing which columns to display seem like two separate actions, so it’s unexpected that one affects the other in this way. I’d expect the filters to stay active regardless of which columns are currently visible. Losing filter state just by switching a saved table config can be frustrating, especially when a lot of time was spent setting up those filters. Even if the filtered column is hidden, the filtering is still meaningful and often necessary—having the ability to preserve it, even with a subtle warning or indicator, would greatly improve the UX.
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 type: feature
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#11232
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?