Global to model refined search #7779

Closed
opened 2025-12-29 20:28:04 +01:00 by adam · 2 comments
Owner

Originally created by @PieterL75 on GitHub (Mar 21, 2023).

NetBox version

v3.4.5

Feature type

Data model extension

Proposed functionality

With the new search, the option to go to the 'Refine Search' is gone.
This was a very handy feature. If the search result returned what you needed, it brought you direct to the details page of the model.

I would like to make the 'model' column of the global search a link, that brings you to the model-list with the filter applied.
image
In the above image, the 'Device' could become a link that brings you to https://demo.netbox.dev/dcim/devices/?q=-rtr

The only caveat is the Lookup type... if using anything else then partial, it will return different values in the model-search

Use case

One-click forward to details of the searchresult

Database changes

No response

External dependencies

No response

Originally created by @PieterL75 on GitHub (Mar 21, 2023). ### NetBox version v3.4.5 ### Feature type Data model extension ### Proposed functionality With the new search, the option to go to the 'Refine Search' is gone. This was a very handy feature. If the search result returned what you needed, it brought you direct to the details page of the model. I would like to make the 'model' column of the global search a link, that brings you to the model-list with the filter applied. ![image](https://user-images.githubusercontent.com/74899468/226554892-12fb1d3d-3ae9-42b5-b918-711ea457d75c.png) In the above image, the 'Device' could become a link that brings you to https://demo.netbox.dev/dcim/devices/?q=-rtr The only caveat is the Lookup type... if using anything else then partial, it will return different values in the model-search ### Use case One-click forward to details of the searchresult ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:28:04 +01:00
adam closed this issue 2025-12-29 20:28:04 +01:00
Author
Owner

@jeremystretch commented on GitHub (Mar 21, 2023):

With the new search, the option to go to the 'Refine Search' is gone. This was a very handy feature. If the search result returned what you needed, it brought you direct to the details page of the model.

This button existed solely because each model necessitated a separate query, and each query was limited to returning a fixed number (20, IIRC) of results. There was no option to display more than the fixed number of results, so the button was provided to show all the results for a specific object type. This is no longer necessary, because the improved global search returns all results, ordered by relevance.

I would like to make the 'model' column of the global search a link, that brings you to the model-list with the filter applied.

Two problems with this:

  1. Embedding a link on each row suggests that the link relates to that specific object. In this case, it would not, which makes for poor UX.
  2. The global search and model-specific searches implement different logic, so each will potentially return different results in a different order.
@jeremystretch commented on GitHub (Mar 21, 2023): > With the new search, the option to go to the 'Refine Search' is gone. This was a very handy feature. If the search result returned what you needed, it brought you direct to the details page of the model. This button existed solely because each model necessitated a separate query, and each query was limited to returning a fixed number (20, IIRC) of results. There was no option to display more than the fixed number of results, so the button was provided to show all the results for a specific object type. This is no longer necessary, because the improved global search returns _all_ results, ordered by relevance. > I would like to make the 'model' column of the global search a link, that brings you to the model-list with the filter applied. Two problems with this: 1. Embedding a link on each row suggests that the link relates to that specific object. In this case, it would not, which makes for poor UX. 2. The global search and model-specific searches implement different logic, so each will potentially return different results in a different order.
Author
Owner

@jeremystretch commented on GitHub (May 4, 2023):

I'm going to close this out as the proposed implementation doesn't appear to be feasible and there's been no further discussion.

@jeremystretch commented on GitHub (May 4, 2023): I'm going to close this out as the proposed implementation doesn't appear to be feasible and there's been no further discussion.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7779