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

Optionally set a user global search preference #11817

New Issue
Open
opened 2025-12-29 21:50:15 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:50:15 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Nov 7, 2025).

NetBox version

v4.3.7

Feature type

Data model extension

Proposed functionality

I'd like to reopen the FR #17138

The default GlobalSearch Lookup Type is set to partial match.
While this is in most cases good enough, there are also a lot of cases where it just does not cut it.

The proposal is to implement an extra User-Profile based setting that sets the default LookupType for that user.

The concern was that this could confuse users on the results.
To improve that, the resulting URL should include the used lookuptype, so that it can be passed to other users (that have a different default setting).

Use case

In our company, most lookups are regex based, and not contains.
A very common search is esx*.datacenter or rtr*.customer
Each time this search is performed, a second action is needed to change the search type to regex in stead of contains.

Setting the default per user, can reduce the UI interaction, provide consistent result for that user and the why can't this be defaulted question from my users.

Database changes

An extra UserProfile field is required to store the LookupType default.

External dependencies

No response

Originally created by @PieterL75 on GitHub (Nov 7, 2025). ### NetBox version v4.3.7 ### Feature type Data model extension ### Proposed functionality I'd like to reopen the FR #17138 The default GlobalSearch Lookup Type is set to partial match. While this is in most cases good enough, there are also a lot of cases where it just does not cut it. The proposal is to implement an extra User-Profile based setting that sets the default LookupType for that user. The concern was that this could confuse users on the results. To improve that, the resulting URL should include the used lookuptype, so that it can be passed to other users (that have a different default setting). ### Use case In our company, most lookups are `regex` based, and not `contains`. A very common search is `esx*.datacenter` or `rtr*.customer` Each time this search is performed, a second action is needed to change the search type to regex in stead of contains. Setting the default per user, can reduce the UI interaction, provide consistent result for that user and the `why can't this be defaulted` question from my users. ### Database changes An extra UserProfile field is required to store the LookupType default. ### External dependencies _No response_
adam added the type: featurenetboxstatus: backlog labels 2025-12-29 21:50:15 +01:00
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 netbox status: backlog 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#11817
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?