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

Search results page column customisation #8495

New Issue
Closed
opened 2025-12-29 20:37:25 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:37:25 +01:00
Owner
Copy Link

Originally created by @andyb2000 on GitHub (Aug 22, 2023).

NetBox version

v3.4.6

Feature type

New functionality

Proposed functionality

On the search results page (/search/?q=test) it would be useful to be able to specify the columns shown to the user, preferable by a configuration.py configurable option to give further information on the results.
The principle is when returning data it can be confusing to know which element to click on when multiple devices share similar descriptions (value column).

Use case

Take for example when searching for a specific description that appears on multiple switches, you'd receive a list similar to:

<html>
Type Object Field Value
Interface GigabitEthernet1/0/4 (gi1/0/4) Description Customer: MyClientInterface - customer data
Interface GigabitEthernet1/0/4 (gi1/0/4) Description Customer: MyClientInterface - customer data
</html>

In the above the two interfaces are on separate devices and you cannot see that on the results display, so adding a column of the device (or being able to customise) would be useful.

Database changes

No response

External dependencies

No response

Originally created by @andyb2000 on GitHub (Aug 22, 2023). ### NetBox version v3.4.6 ### Feature type New functionality ### Proposed functionality On the search results page (/search/?q=test) it would be useful to be able to specify the columns shown to the user, preferable by a configuration.py configurable option to give further information on the results. The principle is when returning data it can be confusing to know which element to click on when multiple devices share similar descriptions (value column). ### Use case Take for example when searching for a specific description that appears on multiple switches, you'd receive a list similar to: <html> <body> <!--StartFragment--> Type | Object | Field | Value -- | -- | -- | -- Interface | GigabitEthernet1/0/4 (gi1/0/4) | Description | Customer: MyClientInterface - customer data Interface | GigabitEthernet1/0/4 (gi1/0/4) | Description | Customer: MyClientInterface - customer data <!--EndFragment--> </body> </html> In the above the two interfaces are on separate devices and you cannot see that on the results display, so adding a column of the device (or being able to customise) would be useful. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:37:25 +01:00
adam closed this issue 2025-12-29 20:37:25 +01:00
adam commented 2025-12-29 20:37:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 23, 2023):

What you're describing is not feasible for the global search, which can return many different types of objects. For example, what if your results include two interfaces, a rack, three VLANs, and a tenant?

@jeremystretch commented on GitHub (Aug 23, 2023): What you're describing is not feasible for the global search, which can return many different types of objects. For example, what if your results include two interfaces, a rack, three VLANs, and a tenant?
adam commented 2025-12-29 20:37:27 +01:00
Author
Owner
Copy Link

@andyb2000 commented on GitHub (Aug 23, 2023):

Yes, I was aware that it's a multi-function results page, but having an optional column (even if blank) for specific fields would help end-users out hugely when results are returned, at the moment the search pages cause confusion.

@andyb2000 commented on GitHub (Aug 23, 2023): Yes, I was aware that it's a multi-function results page, but having an optional column (even if blank) for specific fields would help end-users out hugely when results are returned, at the moment the search pages cause confusion.
adam commented 2025-12-29 20:37:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 23, 2023):

Following this strategy would quickly result in dozens of (mostly empty) columns across as many different models. The global search results would turn into a giant unreadable mess. Imagine having to side scroll through a dozen empty columns just to find something relevant to a specific result.

@jeremystretch commented on GitHub (Aug 23, 2023): Following this strategy would quickly result in dozens of (mostly empty) columns across as many different models. The global search results would turn into a giant unreadable mess. Imagine having to side scroll through a dozen empty columns just to find something relevant to a specific result.
adam commented 2025-12-29 20:37:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 13, 2023):

I'm going to close this out as the proposed implementation does not seem feasible.

@jeremystretch commented on GitHub (Oct 13, 2023): I'm going to close this out as the proposed implementation does not seem feasible.
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#8495
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?