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

Allow selection of results to filter by model on new global search #7393

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

Originally created by @mmfreitas on GitHub (Dec 20, 2022).

NetBox version

v3.4.1

Feature type

Change to existing functionality

Proposed functionality

First of all congrats on the new global search, amazing work!

In my opinion there is just a functionality missing that was very useful in the old search.
In the old global search engine, I found very useful the fact that I could search for something and then use the provided button to filter the results for a specific model, and then update the provided results at once.

Is it possible to in the new global search, implement this funcionality? Maybe by adding a checkbox on the results and allow the selection to provide an edit for each model?

Use case

Having a quick way to, from global search results, select multiple instances for updating or deleting records.

Database changes

No response

External dependencies

No response

Originally created by @mmfreitas on GitHub (Dec 20, 2022). ### NetBox version v3.4.1 ### Feature type Change to existing functionality ### Proposed functionality First of all congrats on the new global search, amazing work! In my opinion there is just a functionality missing that was very useful in the old search. In the old global search engine, I found very useful the fact that I could search for something and then use the provided button to filter the results for a specific model, and then update the provided results at once. Is it possible to in the new global search, implement this funcionality? Maybe by adding a checkbox on the results and allow the selection to provide an edit for each model? ### Use case Having a quick way to, from global search results, select multiple instances for updating or deleting records. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:22:53 +01:00
adam closed this issue 2025-12-29 20:22:54 +01:00
adam commented 2025-12-29 20:22:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

What you're describing isn't really feasible under the new search engine, as results are now ranked by relevance without regard to object type. However, the legacy search behavior you describe is still available under each model-specific list view.

@jeremystretch commented on GitHub (Dec 22, 2022): What you're describing isn't really feasible under the new search engine, as results are now ranked by relevance without regard to object type. However, the legacy search behavior you describe is still available under each model-specific list view.
adam commented 2025-12-29 20:22:55 +01:00
Author
Owner
Copy Link

@mmfreitas commented on GitHub (Dec 22, 2022):

What you're describing isn't really feasible under the new search engine, as results are now ranked by relevance without regard to object type. However, the legacy search behavior you describe is still available under each model-specific list view.

I see, maybe it's just an issue of the user getting accustomed to this, the shortcut was very handy though!
Thank you for your quick reply. You may close this if you wish :)

@mmfreitas commented on GitHub (Dec 22, 2022): > What you're describing isn't really feasible under the new search engine, as results are now ranked by relevance without regard to object type. However, the legacy search behavior you describe is still available under each model-specific list view. I see, maybe it's just an issue of the user getting accustomed to this, the shortcut was very handy though! Thank you for your quick reply. You may close this if you wish :)
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#7393
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?