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

Change the display name of the "Filter" field at the top of searchable tables to "Search" #5428

New Issue
Closed
opened 2025-12-29 19:27:51 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:27:51 +01:00
Owner
Copy Link

Originally created by @jhammond-git on GitHub (Sep 27, 2021).

NetBox version

v3.0.3

Feature type

Change to existing functionality

Proposed functionality

I didn't feel comfortable calling this a bug, but using "Filter" as a display name for the field at the top of searchable tables causes confusion with actual filters useable from the "Filter" tab.

The field could be called "Search", or "Search results", or something similar to separate it from actual filters.

Use case

This separates the search field from the function of the Filters tab in the UI, and reduces confusion for users trying to take action on a filtered list of objects.

Database changes

None. Just a display change.

External dependencies

None.

Originally created by @jhammond-git on GitHub (Sep 27, 2021). ### NetBox version v3.0.3 ### Feature type Change to existing functionality ### Proposed functionality I didn't feel comfortable calling this a bug, but using "Filter" as a display name for the field at the top of searchable tables causes confusion with actual filters useable from the "Filter" tab. The field could be called "Search", or "Search results", or something similar to separate it from actual filters. ### Use case This separates the search field from the function of the Filters tab in the UI, and reduces confusion for users trying to take action on a filtered list of objects. ### Database changes None. Just a display change. ### External dependencies None.
adam added the type: feature label 2025-12-29 19:27:51 +01:00
adam closed this issue 2025-12-29 19:27:51 +01:00
adam commented 2025-12-29 19:27:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 27, 2021):

It's a valid point. Maybe it would make more sense to rename the "Filters" tab to "Search?" I think there's been some confusion over what the filter widget actually does, but IMO "filter" is more accurate for it.

@jeremystretch commented on GitHub (Sep 27, 2021): It's a valid point. Maybe it would make more sense to rename the "Filters" tab to "Search?" I think there's been some confusion over what the filter widget actually does, but IMO "filter" is more accurate for it.
adam commented 2025-12-29 19:27:51 +01:00
Author
Owner
Copy Link

@jhammond-git commented on GitHub (Sep 27, 2021):

In my opinion, "Filter" is fine for the static tab function. The UI's that I've seen with both types of functions call the static function "Filter(s)", and use the dynamic field for "Search within results..." Since you always have a dynamic field, I suggested simply "Search", but maybe users would be less confused by "Search within results..." than by "Filter".

I am not a UI designer.

@jhammond-git commented on GitHub (Sep 27, 2021): In my opinion, "Filter" is fine for the static tab function. The UI's that I've seen with both types of functions call the static function "Filter(s)", and use the dynamic field for "Search within results..." Since you always have a dynamic field, I suggested simply "Search", but maybe users would be less confused by "Search within results..." than by "Filter". I am not a UI designer.
adam commented 2025-12-29 19:27:52 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 28, 2021):

Perhaps "Filter current displayed results"?

@DanSheps commented on GitHub (Sep 28, 2021): Perhaps "Filter current displayed results"?
adam commented 2025-12-29 19:27:52 +01:00
Author
Owner
Copy Link

@jhammond-git commented on GitHub (Sep 30, 2021):

I feel like any use of "Filter" in the dynamic search field will continue the confusion. "Search displayed results" sounds reasonable, though.

@jhammond-git commented on GitHub (Sep 30, 2021): I feel like any use of "Filter" in the dynamic search field will continue the confusion. "Search displayed results" sounds reasonable, though.
adam commented 2025-12-29 19:27:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

I'm going to fold this under #7450 as part of a larger effort to clean up various parts of the UI.

@jeremystretch commented on GitHub (Oct 5, 2021): I'm going to fold this under #7450 as part of a larger effort to clean up various parts of the UI.
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#5428
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?