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

Make Custom Field Choices searchable #11476

New Issue
Closed
opened 2025-12-29 21:45:46 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:45:46 +01:00
Owner
Copy Link

Originally created by @abrahamvegh on GitHub (Aug 12, 2025).

NetBox version

v4.3.6

Feature type

Change to existing functionality

Proposed functionality

Custom Fields are exposed in global search, but Custom Field Choices are not currently.

Use case

Make users feel more sane when they search for a value they know to be present in a Custom Field Choice? 😅

This omission feels like an oversight.

Database changes

No response

External dependencies

No response

Originally created by @abrahamvegh on GitHub (Aug 12, 2025). ### NetBox version v4.3.6 ### Feature type Change to existing functionality ### Proposed functionality Custom Fields are exposed in global search, but Custom Field Choices are not currently. ### Use case Make users feel more sane when they search for a value they know to be present in a Custom Field Choice? 😅 This omission feels like an oversight. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:45:46 +01:00
adam closed this issue 2025-12-29 21:45:46 +01:00
adam commented 2025-12-29 21:45:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 14, 2025):

I'm not sure it makes sense to include these in global search; one can imagine it getting pretty noisy. Is it not sufficient to use the specific choice filter to find these (e.g. /extras/custom-field-choices/?choice=foo)?

@jeremystretch commented on GitHub (Aug 14, 2025): I'm not sure it makes sense to include these in global search; one can imagine it getting pretty noisy. Is it not sufficient to use the specific `choice` filter to find these (e.g. `/extras/custom-field-choices/?choice=foo`)?
adam commented 2025-12-29 21:45:47 +01:00
Author
Owner
Copy Link

@abrahamvegh commented on GitHub (Aug 15, 2025):

I can definitely respect the desire to minimize noise in global search.

I think I’m confused about what level of preference is given to which fields/values are searchable.

For example, I have a custom field that stores a date, and searching for that precise date returns all of the objects with that value in that custom field.

However, certain built-in fields (e.g. circuit.install_date) are not exposed via search.

choice filter

That only shows me the choice set containing the choice; I was looking for objects whose field has that value assigned.

@abrahamvegh commented on GitHub (Aug 15, 2025): I can definitely respect the desire to minimize noise in global search. I think I’m confused about what level of preference is given to which fields/values are searchable. For example, I have a custom field that stores a date, and searching for that precise date returns all of the objects with that value in that custom field. However, certain built-in fields (e.g. `circuit.install_date`) are *not* exposed via search. > `choice` filter That only shows me the choice set containing the choice; I was looking for objects whose field has that value assigned.
adam commented 2025-12-29 21:45:47 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Aug 22, 2025):

@abrahamvegh, what would prevent you from making some of the custom fields into model fields for an existing model or custom plugin and then making that globally searchable?

@mr1716 commented on GitHub (Aug 22, 2025): @abrahamvegh, what would prevent you from making some of the custom fields into model fields for an existing model or custom plugin and then making that globally searchable?
adam commented 2025-12-29 21:45:47 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Sep 16, 2025):

To reduce noise, we could add a boolean searchable property to each CustomField so users can decide.

@llamafilm commented on GitHub (Sep 16, 2025): To reduce noise, we could add a boolean `searchable` property to each CustomField so users can decide.
adam commented 2025-12-29 21:45:48 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 2, 2025):

Custom field choice values are searchable through the filters on the objects that use them. Adding them to global search would return far more noise than signal given the high number of choice values across different custom fields and object types. We don't make built-in choice field values searchable for the same reason.

@jnovinger commented on GitHub (Oct 2, 2025): Custom field choice values are searchable through the filters on the objects that use them. Adding them to global search would return far more noise than signal given the high number of choice values across different custom fields and object types. We don't make built-in choice field values searchable for the same reason.
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#11476
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?