UI: Add some sort of "current context" to netbox #1284

New Issue

MrUnknownDE · 2026-04-05T22:55:13+02:00

MrUnknownDE commented

2026-04-05 22:55:13 +02:00

Originally created by @mc on 9/10/2025

NetBox version

4.2.9

Feature type

Other

Proposed functionality

I propose to add some sort of "current context" to netbox, in the form of

a) a dropdown in the top line of netbox, maybe directly left to the dark/bright mode switcher, that enables the user to select (and deselect, including a DESELECT ALL shortcut) a

tenant,
VRF,
... something else that makes sense?

b) that selection will affect:

I) searches, by automatically limiting searches to those set contexts; OR prioritising hits that match the context.
II) lists of children (for example the IP-Addresses tab in a Prefix), by subtly "greying out" items that do not belong to this context
III) creation of new items, by automatically defaulting the fields that are actively set in the context to the values set in the context.

Use case

I often find myself overwhelmed with irrelevant information from tenants or VRFs that I am not interested in, I can apply filters, but when looking for multiple things in succession it needs to be set every time, which is annoying.

Also when creating multiple items it is annoying to have to manually set it over and over again, instead of being automatically filled.

in lists, it aids in finding related and remotely-related objects.

Database changes

none needed, I guess, this seems to be purely an UI thing, with some JS magic to auto-apply the set values to a number of fields in forms.

External dependencies

none either, I guess.

*Originally created by @mc on 9/10/2025* ### NetBox version 4.2.9 ### Feature type Other ### Proposed functionality I propose to add some sort of "current context" to netbox, in the form of a) a dropdown in the top line of netbox, maybe directly left to the dark/bright mode switcher, that enables the user to select (and deselect, including a DESELECT ALL shortcut) a - tenant, - VRF, - ... something else that makes sense? b) that selection will affect: I) searches, by automatically limiting searches to those set contexts; OR prioritising hits that match the context. II) lists of children (for example the IP-Addresses tab in a Prefix), by subtly "greying out" items that do not belong to this context III) creation of new items, by automatically defaulting the fields that are actively set in the context to the values set in the context. ### Use case I often find myself overwhelmed with irrelevant information from tenants or VRFs that I am not interested in, I can apply filters, but when looking for multiple things in succession it needs to be set every time, which is annoying. Also when creating multiple items it is annoying to have to manually set it over and over again, instead of being automatically filled. in lists, it aids in finding related and remotely-related objects. ### Database changes none needed, I guess, this seems to be purely an UI thing, with some JS magic to auto-apply the set values to a number of fields in forms. ### External dependencies none either, I guess.

MrUnknownDE closed this issue

2026-04-05 22:55:13 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

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

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1284