starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-02-26 02:35:12 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-12-29 21:47:21 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:47:21 +01:00
Owner
Copy Link

Originally created by @mc on GitHub (Sep 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 GitHub (Sep 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.
adam added the type: feature label 2025-12-29 21:47:21 +01:00
adam closed this issue 2025-12-29 21:47:21 +01:00
adam commented 2025-12-29 21:47:22 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 11, 2025):

This would be better as a discussion as the exact proposed solution would need to be discussed and evaluated by the community. Switching this over to discussion

@arthanson commented on GitHub (Sep 11, 2025): This would be better as a discussion as the exact proposed solution would need to be discussed and evaluated by the community. Switching this over to discussion
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#11595
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?