Provide a configuration option to include inventory items in the global search #4477

New Issue

adam · 2025-12-29T18:36:26+01:00

adam commented

2025-12-29 18:36:26 +01:00

Originally created by @cpmills1975 on GitHub (Jan 20, 2021).

Environment

Python version: 3.9
NetBox version: 2.10.3

Proposed Functionality

I know that inventory items are explicitly excluded from the global search for efficiency reasons. However, this needs to be balanced with usability and, as a relatively light user of inventory items, I'd like to be able to try and see if adding these in to the global search negatively impacts the speed of the search or not.

Some users will use inventory items extensively and forcing the search to include these may negatively impact the search experience. I do not (4000 odd devices, at the moment maybe <100 inventory items across the entire estate - I am not yet recording every single line card or every single Hard Disk in every single device!).

I'd like the option, through the configuration to globally include or exclude inventory items from the main search.

Use Case

The only inventory items I have recorded so far are high value line cards that are individually asset labelled - I'd like to be able to search for an asset tag regardless of whether it is a device or an inventory item through the main search form and (assuming I know nothing about an asset tag) not have to search for it twice - once in the main search form or the devices page and again in the inventory items page.

Database Changes

None

External Dependencies

None

Originally created by @cpmills1975 on GitHub (Jan 20, 2021).  ### Environment * Python version: 3.9 * NetBox version: 2.10.3  ### Proposed Functionality I know that inventory items are explicitly excluded from the global search for efficiency reasons. However, this needs to be balanced with usability and, as a relatively light user of inventory items, I'd like to be able to try and see if adding these in to the global search negatively impacts the speed of the search or not. Some users will use inventory items extensively and forcing the search to include these may negatively impact the search experience. I do not (4000 odd devices, at the moment maybe <100 inventory items across the entire estate - I am not yet recording every single line card or every single Hard Disk in every single device!). I'd like the option, through the configuration to globally include or exclude inventory items from the main search.  ### Use Case The only inventory items I have recorded so far are high value line cards that are individually asset labelled - I'd like to be able to search for an asset tag regardless of whether it is a device or an inventory item through the main search form and (assuming I know nothing about an asset tag) not have to search for it twice - once in the main search form or the devices page and again in the inventory items page.  ### Database Changes None  ### External Dependencies None

adam closed this issue

2025-12-29 18:36:26 +01:00

adam commented

2025-12-29 18:36:27 +01:00

@jeremystretch commented on GitHub (Jan 20, 2021):

It would not be prudent to introduce a configuration parameter for such a niche change in behavior, especially to deliver relatively little value. (That's how you end up with a thousand little knobs and switches that are nearly impossible to maintain over time.)

A better approach might be to improve the global search form to allow the selection of a subset of models, with the currently available models serving as defaults, and extend it to support inventory items and other models. However, this would need to be fleshed out in a separate FR.

@jeremystretch commented on GitHub (Jan 20, 2021): It would not be prudent to introduce a configuration parameter for such a niche change in behavior, especially to deliver relatively little value. (That's how you end up with a thousand little knobs and switches that are nearly impossible to maintain over time.) A better approach might be to improve the global search form to allow the selection of a subset of models, with the currently available models serving as defaults, and extend it to support inventory items and other models. However, this would need to be fleshed out in a separate FR.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#4477